Triple
T9572432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heterocongridae |
E230955
|
entity |
| Predicate | waterZone |
P7312
|
FINISHED |
| Object | neritic zone |
—
|
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: neritic zone | Statement: [Heterocongridae, waterZone, neritic zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterZone Context triple: [Heterocongridae, waterZone, neritic zone]
-
A.
waterSport
Indicates participation in or association with a sport or recreational activity that takes place on or in water.
-
B.
waterColumnZone
chosen
Indicates the specific vertical region or layer within a body of water where an entity or process is located or occurs.
-
C.
hasWaterActivity
Indicates that one entity possesses, exhibits, or is characterized by a particular level or type of water-related activity (such as moisture content, water availability, or water-based processes).
-
D.
openWaterSwimmingVenue
Indicates that a location serves as a venue where open water swimming activities or events take place.
-
E.
waterbodyOnCourse
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
- 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_69ca847f22188190a56e4a97625bef22 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd998d79cc8190b94e5953915a5fa4 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:04 p.m.