Triple
T29348539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissioner Julius Enderby |
E744237
|
entity |
| Predicate | relationshipToElijahBaley |
P203151
|
FINISHED |
| Object | administrative superior |
—
|
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: administrative superior | Statement: [Commissioner Julius Enderby, relationshipToElijahBaley, administrative superior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToElijahBaley Context triple: [Commissioner Julius Enderby, relationshipToElijahBaley, administrative superior]
-
A.
relationshipToKlaatu
Indicates the specific familial, social, or professional relationship that one entity has to the entity named Klaatu.
-
B.
relationshipToEleanorVance
Indicates the specific nature or type of relationship an entity has with Eleanor Vance.
-
C.
relationshipToMarkWatney
Indicates the specific type of personal or social relationship an entity has with Mark Watney.
-
D.
relationshipToEva
Indicates a specified type of personal or social relationship that an entity has with Eva.
-
E.
relationshipToEliDavid
Indicates the specific familial, professional, or personal relationship that an entity has with Eli David.
- F. None of above. chosen
Provenance (4 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a01295195748190b896d99c3d1f6134 |
completed | May 11, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_6a0128fe96dc8190a73715ab08752dd1 |
completed | May 11, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_6a012950e8d48190a9dc1105fe7a5fb3 |
completed | May 11, 2026, 12:56 a.m. |
Created at: April 28, 2026, 2:04 p.m.