Triple
T18021276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parasympathetic nervous system |
E431121
|
entity |
| Predicate | effectOnPupil |
P51923
|
FINISHED |
| Object | pupillary constriction |
—
|
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: pupillary constriction | Statement: [Parasympathetic nervous system, effectOnPupil, pupillary constriction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnPupil Context triple: [Parasympathetic nervous system, effectOnPupil, pupillary constriction]
-
A.
eyeType
Indicates the specific kind or category of eyes an entity has, such as their form, structure, or visual style.
-
B.
eyePatch
Indicates that one entity wears or has an eye patch, typically covering one of their eyes.
-
C.
eyeCharacteristic
chosen
Indicates a relationship where an entity possesses a specific attribute, feature, or quality of its eyes.
-
D.
eyeMigration
Indicates the movement or displacement of an eye (or eyes) from one position to another within an organism’s body or visual system.
-
E.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c299c48190b0cceecf77cb6de9 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.