Triple
T38261529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42 Tokyo |
E1017939
|
entity |
| Predicate | hasGlobalPeers |
P190591
|
FINISHED |
| Object | 42 Paris |
—
|
NE NERFINISHED |
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: 42 Paris | Statement: [42 Tokyo, hasGlobalPeers, 42 Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalPeers Context triple: [42 Tokyo, hasGlobalPeers, 42 Paris]
-
A.
hasGlobalPriorityPeer
Indicates that one entity is designated as a globally prioritized peer or counterpart relative to another entity.
-
B.
hasGlobalHost
Indicates that an entity is associated with or served by a host that is accessible or applicable at a global (system-wide or worldwide) level.
-
C.
hasGlobalOwner
Indicates that an entity is owned or controlled by a global-level owner, rather than a local or specific one.
-
D.
hasGlobalNetworkType
Indicates that an entity is associated with a specific type or category of global network.
-
E.
hasGlobalIdentity
Indicates that an entity possesses a unique, overarching identity that is recognized or valid across multiple systems, contexts, or domains.
- F. None of above. chosen
Provenance (4 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.