Triple
T38373592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMAR |
E893554
|
entity |
| Predicate | targetsSpeciesGroup |
P97582
|
FINISHED |
| Object | sea turtles |
—
|
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: sea turtles | Statement: [CMAR, targetsSpeciesGroup, sea turtles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsSpeciesGroup Context triple: [CMAR, targetsSpeciesGroup, sea turtles]
-
A.
speciesGrouping
Indicates a relationship where multiple organisms are classified or organized together based on shared species-level characteristics or taxonomic criteria.
-
B.
taxonGroup
Indicates a classification relationship where one taxon is grouped within or associated with a broader taxonomic group.
-
C.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
D.
supportsSpeciesGroup
Indicates that one entity provides suitable conditions or resources that enable the survival or persistence of a particular group of species.
-
E.
typicalTargetSpecies
chosen
Indicates the species that is most commonly or characteristically targeted or affected by a given action, process, or agent.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.