Triple
T27461432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Cavalry vs. Apaches |
E692755
|
entity |
| Predicate | commonInMedium |
P22599
|
FINISHED |
| Object | Hollywood Western films |
—
|
NE NERFINISHED |
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: Hollywood Western films | Statement: [U.S. Cavalry vs. Apaches, commonInMedium, Hollywood Western films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonInMedium Context triple: [U.S. Cavalry vs. Apaches, commonInMedium, Hollywood Western films]
-
A.
commonMedium
chosen
Indicates that two or more entities share the same medium or channel through which interaction, communication, or transmission occurs.
-
B.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
C.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
D.
commonLevel
Indicates that two or more entities share the same level, rank, or hierarchical position within a given system or structure.
-
E.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 12:50 p.m.