Triple
T29616189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archimedes' Dial |
E754870
|
entity |
| Predicate | hasComponentInFiction |
P106216
|
FINISHED |
| Object | two-part mechanism |
—
|
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: two-part mechanism | Statement: [Archimedes' Dial, hasComponentInFiction, two-part mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentInFiction Context triple: [Archimedes' Dial, hasComponentInFiction, two-part mechanism]
-
A.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
B.
hasFeatureInFiction
chosen
Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
-
C.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
-
D.
hasRelativeInFiction
Indicates that one entity has a relative or family member who appears as a character within a fictional work associated with the other entity.
-
E.
hasChildInFiction
Indicates that a fictional work or character includes another character as their child within the fictional narrative.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: April 28, 2026, 6:31 p.m.