Triple
T34934153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandaean mandi |
E1007520
|
entity |
| Predicate | associatedWithWater |
P130982
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mandaean mandi, associatedWithWater, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWater Context triple: [Mandaean mandi, associatedWithWater, yes]
-
A.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
B.
associatedWithWaterfront
Indicates a relationship in which something is located on, adjacent to, or otherwise directly connected with a waterfront area.
-
C.
hasWaterRelatedActivity
Indicates that an entity engages in, offers, or is associated with an activity involving water (e.g., swimming, boating, or other water-based actions).
-
D.
associatedWithSea
Indicates a relationship in which something has a connection, relevance, or linkage to the sea or marine environment.
-
E.
relationshipToWater
chosen
Indicates the nature or type of connection an entity has with water, such as dependence on, interaction with, or effect upon 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.