Triple
T33115233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MURR |
E847441
|
entity |
| Predicate | hasCoreLocation |
P42732
|
FINISHED |
| Object | underwater pool |
—
|
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: underwater pool | Statement: [MURR, hasCoreLocation, underwater pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreLocation Context triple: [MURR, hasCoreLocation, underwater pool]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasLocationComponent
chosen
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
C.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
D.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
-
E.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.