Triple
T527980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell Conference |
E10964
|
entity |
| Predicate | renamedToReflect |
P15210
|
FINISHED |
| Object | geographic naming convention |
—
|
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: geographic naming convention | Statement: [Campbell Conference, renamedToReflect, geographic naming convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedToReflect Context triple: [Campbell Conference, renamedToReflect, geographic naming convention]
-
A.
renamedTo
Indicates that an entity has been given a new name, specifying the target name it was changed to.
-
B.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
C.
reflects
Indicates that one entity (often a surface, medium, or representation) throws back, mirrors, or otherwise shows an image, property, or state of another entity.
-
D.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
-
E.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d2851c81908129f7da932ab7b3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.