Triple
T21781559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobson’s organ |
E537724
|
entity |
| Predicate | oftenWellDevelopedIn |
P145924
|
FINISHED |
| Object | 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: snakes | Statement: [Jacobson’s organ, oftenWellDevelopedIn, snakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenWellDevelopedIn Context triple: [Jacobson’s organ, oftenWellDevelopedIn, snakes]
-
A.
developsUntil
Indicates that a process, condition, or entity continues to develop or progress up to a specified point or limit in time or state.
-
B.
developmentalFor
Indicates that one entity serves as a developmental precursor, stage, or necessary condition for the emergence or maturation of another entity.
-
C.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
D.
developmentalContractedWith
Indicates a formal developmental agreement or contract established between two entities, typically for research, design, or product development activities.
-
E.
developedStructure
Indicates that an entity has created, designed, or brought into existence a particular structure or constructed form.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462db0208190ad31c132d3f875bc |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:52 p.m.