Triple
T1290194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z39.50 |
E27528
|
entity |
| Predicate | typicalTransport |
P1379
|
FINISHED |
| Object | TCP/IP |
—
|
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: TCP/IP | Statement: [Z39.50, typicalTransport, TCP/IP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTransport Context triple: [Z39.50, typicalTransport, TCP/IP]
-
A.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
C.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
D.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
E.
publicTransit
Indicates that one entity provides or is connected via shared, scheduled transportation services (such as buses, trains, or subways) that are available for use by the general public.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d6af908190ade9c481cc6f0ad8 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.