Triple
T4531704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M81 Group |
E106311
|
entity |
| Predicate | containsTidalFeatures |
P57287
|
FINISHED |
| Object | HI gas bridges |
—
|
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: HI gas bridges | Statement: [M81 Group, containsTidalFeatures, HI gas bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTidalFeatures Context triple: [M81 Group, containsTidalFeatures, HI gas bridges]
-
A.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
C.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
D.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
E.
hasBathymetricFeature
Indicates that one entity possesses, contains, or is associated with a specific underwater (seafloor) topographic feature.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579d7a88819083eb0620ca176f2e |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.