Triple
T37664464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Guardian |
E937789
|
entity |
| Predicate | targetPreference |
P199551
|
FINISHED |
| Object | Players |
—
|
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: Players | Statement: [Elder Guardian, targetPreference, Players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPreference Context triple: [Elder Guardian, targetPreference, Players]
-
A.
statedPreference
Indicates that one entity has explicitly expressed or declared a preference for another entity or option.
-
B.
marketPreference
Indicates a relationship where one entity favors, targets, or prioritizes a particular market or market segment over others.
-
C.
establishesPreference
Indicates that one entity selects or favors one option, entity, or condition over another.
-
D.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
E.
endoPreference
Indicates a preference or tendency for something to occur or be located within the interior or internal part of an entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
| PDg | Predicate description generation | batch_69ff4163a8548190b0eaafd0a377b141 |
completed | May 9, 2026, 2:14 p.m. |
Created at: May 3, 2026, 4:18 p.m.