Triple
T14853550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovejoy family |
E349292
|
entity |
| Predicate | roleInPlaceName |
P65288
|
FINISHED |
| Object | local namesake for Lovejoy, Georgia |
—
|
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: local namesake for Lovejoy, Georgia | Statement: [Lovejoy family, roleInPlaceName, local namesake for Lovejoy, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPlaceName Context triple: [Lovejoy family, roleInPlaceName, local namesake for Lovejoy, Georgia]
-
A.
roleAsPlace
chosen
Indicates that an entity functions or is used as a place or location in relation to another entity or event.
-
B.
roleInMovement
Indicates the specific function, position, or contribution an entity has within a broader movement or collective effort.
-
C.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
D.
roleInRhyme
Indicates the specific function or part an entity plays within a rhyme, such as a character, object, or structural element of the rhyming text.
-
E.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44318f0819080b6c599f2d3474f |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.