Triple
T3872076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caenorhabditis elegans |
E92409
|
entity |
| Predicate | connectomeStatus |
P51602
|
FINISHED |
| Object | whole-animal wiring diagram mapped |
—
|
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: whole-animal wiring diagram mapped | Statement: [Caenorhabditis elegans, connectomeStatus, whole-animal wiring diagram mapped]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectomeStatus Context triple: [Caenorhabditis elegans, connectomeStatus, whole-animal wiring diagram mapped]
-
A.
connectsState
Indicates a relationship where one entity serves as a link or conduit between different states, conditions, or statuses of another entity.
-
B.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
C.
collectorStatus
Indicates the current operational or lifecycle state of a collector in relation to its collection activity.
-
D.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
E.
explorationStatus
Indicates the current state or phase of an exploration process or activity between entities.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec5691148190b469af0bee9154db |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:20 p.m.