Triple
T29436493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osborn, Ohio |
E746586
|
entity |
| Predicate | hasBeenAbsorbedBy |
P50531
|
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, hasBeenAbsorbedBy, Fairborn, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenAbsorbedBy Context triple: [Osborn, Ohio, hasBeenAbsorbedBy, Fairborn, Ohio]
-
A.
absorbed
Indicates that one entity takes in, soaks up, or assimilates another entity or substance.
-
B.
demolishedOrAbsorbed
chosen
Indicates that one entity has ceased to exist independently because it was either physically destroyed or organizationally absorbed into another entity.
-
C.
isConsumedBy
Indicates that one entity is eaten, drunk, or otherwise ingested or used up by another entity.
-
D.
allianceAfterAbsorption
Indicates that an alliance relationship is formed between entities after one has absorbed or taken over the other.
-
E.
largelyConsumedBy
Indicates that something is mostly or predominantly eaten or used up by a particular consumer or group.
- 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_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 28, 2026, 3:17 p.m.