Triple
T21615177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montaukett |
E533418
|
entity |
| Predicate | hadEarlyContactWith |
P4255
|
FINISHED |
| Object | European settlers |
—
|
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: European settlers | Statement: [Montaukett, hadEarlyContactWith, European settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadEarlyContactWith Context triple: [Montaukett, hadEarlyContactWith, European settlers]
-
A.
historicalContactWith
chosen
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
B.
hadCommon
Indicates that two or more entities shared the same attribute, experience, or element in common.
-
C.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
D.
hasContactInfluenceFrom
Indicates that one entity’s state, behavior, or properties are directly affected or altered through physical or direct contact with another entity.
-
E.
hadOrgan
Indicates that an entity previously possessed or contained a specific organ as part of its body.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3baab9e88190bc02f27133ef32d6 |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.