Triple
T35134317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Astros |
E1014526
|
entity |
| Predicate | adoptedInTown |
P4186
|
FINISHED |
| Object | Astros |
—
|
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: Astros | Statement: [Constitution of Astros, adoptedInTown, Astros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedInTown Context triple: [Constitution of Astros, adoptedInTown, Astros]
-
A.
adoptedInCity
chosen
Indicates that an adoption event took place within a specific city.
-
B.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
C.
adoptedNear
Indicates that an adoption event occurred at or in close proximity to a specified location or reference point.
-
D.
adoptedInto
Indicates that one entity has been taken in and legally or formally accepted as a member of another entity’s family, group, or organization.
-
E.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:02 p.m.