Triple
T27091584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimetrodon |
E686180
|
entity |
| Predicate | sailFunctionHypothesis |
P161845
|
FINISHED |
| Object | species recognition |
—
|
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: species recognition | Statement: [Dimetrodon, sailFunctionHypothesis, species recognition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sailFunctionHypothesis Context triple: [Dimetrodon, sailFunctionHypothesis, species recognition]
-
A.
sailFunctionHypothesis
chosen
Indicates a hypothesized or proposed functional role or purpose related to sailing or sail operation.
-
B.
functionHypothesis
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
C.
hasSail
Indicates that one entity possesses or is equipped with a sail used for catching wind.
-
D.
sailingUnder
Indicates that one entity (typically a vessel) is operating or traveling while registered, flagged, or officially recognized under the authority or jurisdiction of another entity (such as a country or organization).
-
E.
sails
Indicates that an entity travels over water in a vessel propelled by sails or similar means.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 8:41 a.m.