Triple
T6981843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shompen people |
E161864
|
entity |
| Predicate | degreeOfContact |
P4255
|
FINISHED |
| Object | limited contact with outsiders |
—
|
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: limited contact with outsiders | Statement: [Shompen people, degreeOfContact, limited contact with outsiders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: degreeOfContact Context triple: [Shompen people, degreeOfContact, limited contact with outsiders]
-
A.
hasContactInfluenceFrom
Indicates that one entity’s state, behavior, or properties are directly affected or altered through physical or direct contact with another entity.
-
B.
historicalContactWith
chosen
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
C.
isDegreeOf
Indicates that one entity is an academic or professional degree held, pursued, or associated with another entity.
-
D.
acquaintanceOf
Indicates that one entity knows another in a casual or non-intimate way, without implying close friendship or strong personal ties.
-
E.
hasContactRole
Indicates that an entity serves in a specific role or capacity as a contact for another entity.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db6d3f3c8190b0121f7934440c34 |
completed | March 27, 2026, 7:33 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.