Triple
T14570997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahikan |
E341910
|
entity |
| Predicate | refersToGroupAssociatedWith |
P114713
|
FINISHED |
| Object | rivers |
—
|
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: rivers | Statement: [Mahikan, refersToGroupAssociatedWith, rivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToGroupAssociatedWith Context triple: [Mahikan, refersToGroupAssociatedWith, rivers]
-
A.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
B.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
E.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb5ac548190932f238e37271741 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:23 a.m.