Triple
T31038015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syndyoceras |
E790902
|
entity |
| Predicate | hornFunctionHypothesis |
P14769
|
FINISHED |
| Object | display |
—
|
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: display | Statement: [Syndyoceras, hornFunctionHypothesis, display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hornFunctionHypothesis Context triple: [Syndyoceras, hornFunctionHypothesis, display]
-
A.
functionHypothesis
chosen
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
B.
hypothesis
Indicates that a statement or proposition is tentatively assumed to be true and is subject to testing, evaluation, or proof.
-
C.
primaryFunctionHypothesis
Indicates a hypothesized main role or purpose that one entity is proposed to serve in relation to another or within a given system.
-
D.
sailFunctionHypothesis
Indicates a hypothesized or proposed functional role or purpose related to sailing or sail operation.
-
E.
proposesHypothesis
Indicates that one entity puts forward a tentative explanation or hypothesis for consideration regarding another entity or phenomenon.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694f800e48190bad9640e6896b76b |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.