Triple
T11177214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiphophorus |
E264440
|
entity |
| Predicate | aquariumUse |
P96456
|
FINISHED |
| Object | community aquariums |
—
|
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: community aquariums | Statement: [Xiphophorus, aquariumUse, community aquariums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aquariumUse Context triple: [Xiphophorus, aquariumUse, community aquariums]
-
A.
aquariumSection
Indicates a specific section or area within an aquarium to which something (e.g., an exhibit, organism, or object) is assigned or located.
-
B.
hasCommonAquariumUse
chosen
Indicates that two entities share at least one similar or overlapping use or function within the context of aquariums.
-
C.
aquariumTrade
Indicates that an entity is involved in the commercial trade or collection of organisms for keeping in aquariums.
-
D.
aquariumRequirement
Indicates that an entity has specific needs or conditions related to being kept in an aquarium.
-
E.
containsAquariumFish
Indicates that one entity includes or holds aquarium fish within it.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8987e1081909b28a0bdb866beae |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.