Triple
T38429492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoovers |
E903758
|
entity |
| Predicate | laterAllocatedTo |
P108451
|
FINISHED |
| Object | Western Region |
—
|
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: Western Region | Statement: [Hoovers, laterAllocatedTo, Western Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAllocatedTo Context triple: [Hoovers, laterAllocatedTo, Western Region]
-
A.
allottedTo
chosen
Indicates that something has been assigned or allocated to a particular entity as its designated recipient or user.
-
B.
allottedBy
Indicates that something has been assigned, distributed, or allocated by a particular agent or authority.
-
C.
laterAssignment
Indicates that one entity is assigned or allocated to another at a later time than some reference assignment or event.
-
D.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
-
E.
laterHeldBy
Indicates that an entity was possessed, controlled, or owned by another entity at a subsequent time after an earlier state or holder.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a017114e7148190b7479284c316443d |
completed | May 11, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a016eebd60481909212e2a49ef95fbe |
completed | May 11, 2026, 5:53 a.m. |
Created at: May 3, 2026, 4:31 p.m.