Triple
T9753114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celia Mae |
E236488
|
entity |
| Predicate | hairType |
P90502
|
FINISHED |
| Object | living snakes |
—
|
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: living snakes | Statement: [Celia Mae, hairType, living snakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hairType Context triple: [Celia Mae, hairType, living snakes]
-
A.
hairDetail
Indicates a relationship that specifies particular characteristics or attributes of an entity’s hair, such as style, color, length, or texture.
-
B.
hasHair
Indicates that an entity possesses hair as a physical attribute.
-
C.
hairAsSymbol
Indicates that hair functions as a symbolic element representing ideas, traits, or meanings beyond its literal physical presence.
-
D.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
E.
fiberType
Indicates the specific kind or classification of fiber that characterizes or composes an entity.
- 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fae332c8190b11f0258b5a5ae2b |
completed | April 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:24 p.m.