Triple
T38038829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Route 2 (New Brunswick) |
E949422
|
entity |
| Predicate | twinningCompleted |
P141242
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Route 2 (New Brunswick), twinningCompleted, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: twinningCompleted Context triple: [Route 2 (New Brunswick), twinningCompleted, 2007]
-
A.
hasTwinningCompleted
chosen
Indicates that a twinning process or partnership between entities has been fully carried out and successfully completed.
-
B.
twinning
Indicates that two entities are paired or linked as twins, typically sharing a formally recognized, parallel, or closely matched relationship.
-
C.
hasTwinningStatus
Indicates that there exists a formal or recognized twinning relationship or partnership status between two entities.
-
D.
hasTwinStatus
Indicates that an entity has a twin relationship or classification, such as being one of a pair of twins or having an associated twin counterpart.
-
E.
unificationCompleted
Indicates that a previously initiated unification process between entities has been successfully completed.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.