Triple
T36281623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carapidae |
E892956
|
entity |
| Predicate | minimumLength |
P27681
|
FINISHED |
| Object | about 3 centimetres |
—
|
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 3 centimetres | Statement: [Carapidae, minimumLength, about 3 centimetres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumLength Context triple: [Carapidae, minimumLength, about 3 centimetres]
-
A.
hasMinimumLength
chosen
Indicates that the length of an entity (such as a sequence, string, or collection) is greater than or equal to a specified minimum value.
-
B.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
C.
minimumSize
Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
-
D.
minimumTerm
Indicates the shortest or least duration, period, or term that must apply within a given relationship or agreement.
-
E.
minimumTrackLength
Indicates the smallest allowable or observed length that a track must have within a given context or system.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.