Triple
T32938594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlington, England |
E842602
|
entity |
| Predicate | possibleOriginOfNameOf |
P64092
|
FINISHED |
| Object | Burlington, New Jersey |
—
|
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: Burlington, New Jersey | Statement: [Burlington, England, possibleOriginOfNameOf, Burlington, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleOriginOfNameOf Context triple: [Burlington, England, possibleOriginOfNameOf, Burlington, New Jersey]
-
A.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
B.
possibleNameEtymology
chosen
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
C.
characterNameOrigin
Indicates the source or inspiration from which a character’s name is derived.
-
D.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
E.
natureOfName
Indicates that the relationship specifies the type, origin, or semantic category of a given name.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:20 a.m.