Triple
T30579405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calamity Brook Trail |
E778338
|
entity |
| Predicate | primaryApproachTo |
P203972
|
FINISHED |
| Object | Flowed Lands |
E219068
|
NE 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: Flowed Lands | Statement: [Calamity Brook Trail, primaryApproachTo, Flowed Lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryApproachTo Context triple: [Calamity Brook Trail, primaryApproachTo, Flowed Lands]
-
A.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
B.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
C.
primaryTreatment
Indicates that a specified treatment is the main or first-line intervention used to address a particular condition or problem, as opposed to secondary or adjunctive treatments.
-
D.
standardApproach
Indicates that an entity uses or follows a commonly accepted, conventional, or typical method for addressing a task or problem.
-
E.
primaryReceptionMethod
Indicates the main way in which something is received, accessed, or obtained among multiple possible methods.
- F. None of above. chosen
Provenance (5 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0301c45274819083b0dd9d335f7ee0 |
completed | May 12, 2026, 10:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2863ce9e448190a7393c370b06f96f |
completed | June 9, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a03015c272481908a7bfe81befb1764 |
completed | May 12, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_6a0301c3a34c81909af5de895b1ace80 |
completed | May 12, 2026, 10:32 a.m. |
Created at: April 29, 2026, 8:23 p.m.