Triple
T36390688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mill House |
E896317
|
entity |
| Predicate | relativeEraToArkle |
P201582
|
FINISHED |
| Object | contemporary of Arkle |
—
|
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: contemporary of Arkle | Statement: [Mill House, relativeEraToArkle, contemporary of Arkle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeEraToArkle Context triple: [Mill House, relativeEraToArkle, contemporary of Arkle]
-
A.
associatedWithEraStar
Indicates a relationship where something is linked or connected to a particular era of a star’s existence or development.
-
B.
representedEra
Indicates the historical era or time period that something symbolizes, exemplifies, or stands for.
-
C.
sharesEra
chosen
Indicates that two entities existed, were active, or occurred during the same historical or temporal period.
-
D.
hasApproximateEraOfPlayers
Indicates that two or more players are associated with roughly the same time period or era in which they were active.
-
E.
isBsideOfEra
Indicates that one entity is the B-side counterpart associated with a particular era of another entity (such as a primary release or period).
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.