Triple
T9212370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Saint-Pierre |
E221153
|
entity |
| Predicate | mainHumanActivities |
P1164
|
FINISHED |
| Object | commercial navigation |
—
|
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: commercial navigation | Statement: [Lake Saint-Pierre, mainHumanActivities, commercial navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainHumanActivities Context triple: [Lake Saint-Pierre, mainHumanActivities, commercial navigation]
-
A.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
C.
mannerOfActivity
Indicates the way or style in which an activity is performed or carried out.
-
D.
activityStartApprox
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
E.
activityCorrelatesWith
Indicates that the level or occurrence of one activity is statistically associated with the level or occurrence of another activity, without implying direct causation.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda05406081909893bec3a092d3ce |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.