Triple
T5826148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acton Peninsula land bridge |
E129229
|
entity |
| Predicate | waterBodyTypeCrossed |
P56317
|
FINISHED |
| Object | artificial lake |
—
|
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: artificial lake | Statement: [Acton Peninsula land bridge, waterBodyTypeCrossed, artificial lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyTypeCrossed Context triple: [Acton Peninsula land bridge, waterBodyTypeCrossed, artificial lake]
-
A.
waterwayTypeCrossed
chosen
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
B.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
C.
waterbodyOnCourse
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
-
D.
visitedBodyOfWater
Indicates that an entity has gone to and been physically present at a particular body of water.
-
E.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.