Triple
T1997454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild West |
E43390
|
entity |
| Predicate | notableGroup |
P4297
|
FINISHED |
| Object | cowboys |
—
|
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: cowboys | Statement: [Wild West, notableGroup, cowboys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGroup Context triple: [Wild West, notableGroup, cowboys]
-
A.
notableSubgroup
chosen
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
-
B.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
C.
notableManager
Indicates that an entity has, or is associated with, a manager who is particularly prominent, distinguished, or widely recognized.
-
D.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69a88714cf2c819081644be450b8356e |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.