Triple
T36643721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDSAC |
E904646
|
entity |
| Predicate | hadAssembler |
P78643
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [EDSAC, hadAssembler, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadAssembler Context triple: [EDSAC, hadAssembler, yes]
-
A.
hasAssembler
chosen
Indicates that one entity is responsible for assembling, putting together, or constructing another entity.
-
B.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
C.
hadLocalAssembly
Indicates that an entity hosted or possessed a local-level governing or decision-making assembly within its jurisdiction or area.
-
D.
hasAssemblyLine
Indicates that one entity possesses or operates an assembly line used for producing or assembling items.
-
E.
hadModel
Indicates that an entity possessed, used, or was associated with a particular model (e.g., a product, design, or version) at some point in time.
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.