Triple
T21106359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ridgeville, Ohio |
E520053
|
entity |
| Predicate | laterIncorporatedAs |
P13056
|
FINISHED |
| Object | city |
—
|
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: city | Statement: [North Ridgeville, Ohio, laterIncorporatedAs, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterIncorporatedAs Context triple: [North Ridgeville, Ohio, laterIncorporatedAs, city]
-
A.
laterIncorporated
Indicates that one entity was formally established, merged, or integrated as a legal or organizational body at a later time than another entity or reference point.
-
B.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
C.
textLaterIncorporatedIn
Indicates that one text was subsequently incorporated into, or became part of, another text at a later time.
-
D.
incorporationAfter
Indicates that one entity is incorporated or formally established at a later time than another entity.
-
E.
incorporatedAs
chosen
Indicates that an organization has been legally formed and registered under a specific corporate structure or 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b62301c819082cfc6cb3cd11c8c |
completed | April 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.