Triple
T26824801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manatee exhibit |
E675355
|
entity |
| Predicate | aimsToReplicate |
P64674
|
FINISHED |
| Object | natural manatee habitat |
—
|
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: natural manatee habitat | Statement: [Manatee exhibit, aimsToReplicate, natural manatee habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsToReplicate Context triple: [Manatee exhibit, aimsToReplicate, natural manatee habitat]
-
A.
reproducibility
Indicates that an action, process, or result can be repeated under the same conditions and yield consistent, comparable outcomes.
-
B.
aimsToMeasure
Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
-
C.
aimsToDemonstrate
Indicates an intentional effort by one entity to show, prove, or make evident a particular idea, claim, or outcome to others.
-
D.
aimsToTreat
Indicates that one entity (typically an intervention, treatment, or action) is intended or designed to alleviate, cure, or manage a condition, problem, or target entity.
-
E.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61ad613608190855de13501a86007 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:57 a.m.