Triple
T29436503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osborn, Ohio |
E746586
|
entity |
| Predicate | eventuallyBecamePartOf |
P13314
|
FINISHED |
| Object | Fairborn, Ohio |
—
|
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: Fairborn, Ohio | Statement: [Osborn, Ohio, eventuallyBecamePartOf, Fairborn, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventuallyBecamePartOf Context triple: [Osborn, Ohio, eventuallyBecamePartOf, Fairborn, Ohio]
-
A.
usedToBePartOf
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
-
B.
adoptedAsPartOf
Indicates that one entity has been taken in, integrated, or accepted as a component or member within another entity or larger whole.
-
C.
laterIncorporatedInto
chosen
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
D.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another entity.
-
E.
foundedAsPartOf
Indicates that an entity was established as a component, division, or subset of a larger existing organization, project, or structure.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 3:17 p.m.