Triple
T17181918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stellwag sign |
E417003
|
entity |
| Predicate | hasFindingSite |
P126643
|
FINISHED |
| Object | eyes |
—
|
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: eyes | Statement: [Stellwag sign, hasFindingSite, eyes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFindingSite Context triple: [Stellwag sign, hasFindingSite, eyes]
-
A.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
B.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
C.
hasObservationSite
Indicates that something (such as a measurement, event, or observation activity) is associated with or took place at a specific observation site or location.
-
D.
hasDiscoveryFacility
Indicates that an entity has, is associated with, or is served by a facility where discoveries (such as scientific, medical, or technological findings) are made or were made.
-
E.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc1187808190aeaa0d0e6487957e |
completed | April 18, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:37 a.m.