Triple
T35299744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heath Robinson machine |
E1019470
|
entity |
| Predicate | operationalCodeName |
P2980
|
FINISHED |
| Object | Heath Robinson |
—
|
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: Heath Robinson | Statement: [Heath Robinson machine, operationalCodeName, Heath Robinson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalCodeName Context triple: [Heath Robinson machine, operationalCodeName, Heath Robinson]
-
A.
operationCodeName
chosen
Indicates that an operation is associated with a specific code name used to identify or refer to it.
-
B.
formerCodename
Indicates that one entity was previously used as a codename for another entity, but is no longer its current codename.
-
C.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
-
D.
codenameOwner
Indicates that one entity is the designated owner or holder of the specified codename associated with another entity.
-
E.
usesCodeName
Indicates that one entity refers to another entity by a code name or alias instead of its real or full designation.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a012efebda88190a90c8f650e4b1ee9 |
completed | May 11, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_6a01298cc604819087c836659c128926 |
completed | May 11, 2026, 12:57 a.m. |
Created at: May 3, 2026, 4:03 p.m.