Triple
T18633252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. |
E455473
|
entity |
| Predicate | relationshipToVillagers |
P132476
|
FINISHED |
| Object | ambiguous outsider |
—
|
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: ambiguous outsider | Statement: [K., relationshipToVillagers, ambiguous outsider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToVillagers Context triple: [K., relationshipToVillagers, ambiguous outsider]
-
A.
relationshipToPawneeNation
Indicates the specific type of familial, legal, historical, or political relationship that an entity has with the Pawnee Nation.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationshipToNPC
Indicates the type of interpersonal or narrative connection that one entity has with a non-player character (NPC).
-
D.
relationshipToFriends
Indicates the type or nature of the relationship an entity has with its friends.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc5c7ec8190ab0c64f009583f96 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.