Triple
T30833615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockdale Church |
E785295
|
entity |
| Predicate | namedAfterRelation |
P63
|
FINISHED |
| Object | Rockdale County is named after it |
—
|
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: Rockdale County is named after it | Statement: [Rockdale Church, namedAfterRelation, Rockdale County is named after it]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterRelation Context triple: [Rockdale Church, namedAfterRelation, Rockdale County is named after it]
-
A.
namedForRelationship
Indicates that one entity serves as the namesake or source of the name for another entity.
-
B.
namedAfterField
Indicates that one entity has been given a name derived from or in honor of another entity, typically a person, place, or thing.
-
C.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
D.
namedAfterSuccessor
Indicates that an entity is named after another entity that succeeds or follows it in time, position, or sequence.
-
E.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 29, 2026, 8:45 p.m.