Triple
T1758872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Jurassic |
E38609
|
entity |
| Predicate | marineFaunaIncludes |
P12485
|
FINISHED |
| Object | ichthyosaurs |
—
|
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: ichthyosaurs | Statement: [Early Jurassic, marineFaunaIncludes, ichthyosaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marineFaunaIncludes Context triple: [Early Jurassic, marineFaunaIncludes, ichthyosaurs]
-
A.
hasMarineSpecies
chosen
Indicates that an entity contains, supports, or is associated with one or more marine species.
-
B.
marineLifeTrend
Indicates a change over time in the abundance, health, or distribution of marine life populations.
-
C.
fishFamily
Indicates that one entity is a member of the same biological family (taxonomic family) of fishes as the other entity.
-
D.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
-
E.
hasMarineEcosystem
Indicates that an entity possesses, contains, or is associated with a marine ecosystem as part of its characteristics or environment.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.