Triple
T2114485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FTP |
E42574
|
entity |
| Predicate | dataConnectionDirection |
P9929
|
FINISHED |
| Object | can be server-to-client or client-to-server |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: can be server-to-client or client-to-server | Statement: [FTP, dataConnectionDirection, can be server-to-client or client-to-server]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataConnectionDirection Context triple: [FTP, dataConnectionDirection, can be server-to-client or client-to-server]
-
A.
dataFlowDirection
chosen
Indicates the direction in which data moves or is transmitted from a source entity to a target entity.
-
B.
flowsGenerallyDirection
Indicates that something typically moves or progresses in a particular overall direction, without requiring an exact or constant path.
-
C.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
D.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
E.
netTransportDirection
Indicates the overall direction in which something (such as material, energy, or information) is being transported when considering all contributing flows together.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.