Triple
T23034350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TPC Network |
E573551
|
entity |
| Predicate | hasInternationalLocations |
P28884
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TPC Network, hasInternationalLocations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInternationalLocations Context triple: [TPC Network, hasInternationalLocations, true]
-
A.
hasInternationalOffice
Indicates that an entity maintains an official office or branch located in a foreign country.
-
B.
hasInternationalService
Indicates that an entity provides or is connected to transportation or communication services that operate across national borders.
-
C.
hasInternationalPort
Indicates that an entity possesses a port facility that supports international transportation or trade connections.
-
D.
hasInternationalDistrict
Indicates that an entity possesses, contains, or is associated with a designated international district within its boundaries or scope.
-
E.
operatesInternationally
chosen
Indicates that the entity conducts activities or business across national borders in multiple countries.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18483e5848190977b1bdb1b83d187 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:53 p.m.