Triple
T27635442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toba Aquarium |
E696456
|
entity |
| Predicate | exhibitOrganizationBy |
P164331
|
FINISHED |
| Object | 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: habitat | Statement: [Toba Aquarium, exhibitOrganizationBy, habitat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitOrganizationBy Context triple: [Toba Aquarium, exhibitOrganizationBy, habitat]
-
A.
organizedExhibitionsIn
Indicates that an entity arranged, coordinated, or managed exhibitions that took place in a specified location or venue.
-
B.
areOrganizedBy
Indicates that one entity is responsible for planning, coordinating, or managing the structure or execution of another entity or event.
-
C.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
D.
exhibitFor
Indicates a relationship where something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or entity.
-
E.
exhibitedBy
Indicates that something (such as a quality, behavior, or characteristic) is shown, displayed, or demonstrated by a particular entity.
- F. None of above. chosen
Provenance (4 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 2:23 p.m.