Triple
T3872078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caenorhabditis elegans |
E92409
|
entity |
| Predicate | bodyLengthAdult |
P51603
|
FINISHED |
| Object | about 1 millimeter |
—
|
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: about 1 millimeter | Statement: [Caenorhabditis elegans, bodyLengthAdult, about 1 millimeter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyLengthAdult Context triple: [Caenorhabditis elegans, bodyLengthAdult, about 1 millimeter]
-
A.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
B.
maleLength
Indicates that the relationship specifies the length or size measurement of a male individual or male part of an entity.
-
C.
maximumAdultLength
Indicates the greatest length an organism or entity can reach at full adult size.
-
D.
maxLengthGirth
Indicates that there is a maximum allowable or observed girth (thickness or circumference) associated with the related entity or relationship.
-
E.
averageBodyLengthMale
Indicates the typical or mean body length measured specifically for male individuals of a species or group.
- 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.