Triple
T9572477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyematidae |
E230957
|
entity |
| Predicate | bodyLengthRelative |
P50260
|
FINISHED |
| Object | elongated relative to body depth |
—
|
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: elongated relative to body depth | Statement: [Cyematidae, bodyLengthRelative, elongated relative to body depth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyLengthRelative Context triple: [Cyematidae, bodyLengthRelative, elongated relative to body depth]
-
A.
relativeLength
chosen
Indicates a comparative relationship between entities based on how long they are relative to one another.
-
B.
memberOfBodySize
Indicates that one entity is a component or part whose size contributes to or characterizes the overall body size of another entity.
-
C.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
D.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
E.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998d79cc8190b94e5953915a5fa4 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.