Triple
T18259761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspector Krogh |
E437316
|
entity |
| Predicate | hasMemorableFeature |
P115239
|
FINISHED |
| Object | mechanical wooden arm movement |
—
|
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: mechanical wooden arm movement | Statement: [Inspector Krogh, hasMemorableFeature, mechanical wooden arm movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorableFeature Context triple: [Inspector Krogh, hasMemorableFeature, mechanical wooden arm movement]
-
A.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
B.
memorableProp
chosen
Indicates that something possesses a quality or feature that makes it easy to remember or likely to be recalled.
-
C.
hasMemorableMoments
Indicates that something contains or is associated with particularly notable or unforgettable moments or events.
-
D.
hasMonumentalFeature
Indicates that an entity possesses or includes a significant, large-scale, or historically important physical feature or structure.
-
E.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd89899c8190b8b652c4f61aa5cf |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.