Triple
T2685530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean Reef |
E57474
|
entity |
| Predicate | hasEducationalPurpose |
P27488
|
FINISHED |
| Object | marine conservation awareness |
—
|
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: marine conservation awareness | Statement: [Caribbean Reef, hasEducationalPurpose, marine conservation awareness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEducationalPurpose Context triple: [Caribbean Reef, hasEducationalPurpose, marine conservation awareness]
-
A.
hasEducationalUse
Indicates that something is intended to be used for educational or instructional purposes.
-
B.
hasEducationalAudience
Indicates that something is intended for or directed toward a specific educational audience or learner group.
-
C.
hasEducationalMission
Indicates that an entity is responsible for or engaged in carrying out an educational purpose, goal, or function.
-
D.
hasEducationalFeature
Indicates that something includes or is associated with a component, characteristic, or functionality intended for educational purposes.
-
E.
didacticPurpose
chosen
Indicates that something is intended to teach, instruct, or convey educational content or guidance.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9ef2fe0819082bbe746ca682a7e |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.