Triple
T36322740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noughts + Crosses |
E894378
|
entity |
| Predicate | portraysGroupAsDominant |
P200073
|
FINISHED |
| Object | Crosses |
—
|
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: Crosses | Statement: [Noughts + Crosses, portraysGroupAsDominant, Crosses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysGroupAsDominant Context triple: [Noughts + Crosses, portraysGroupAsDominant, Crosses]
-
A.
imposedDominanceOf
Indicates that one entity has forcibly asserted control, authority, or superiority over another, typically without the latter’s consent.
-
B.
portraysGroup
Indicates that one entity depicts, represents, or visually illustrates a group of entities as its subject.
-
C.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
D.
genderDominance
Indicates a relationship where one gender holds greater power, control, or influence over another within a given context or system.
-
E.
domesticDominance
Indicates a relationship where one entity holds primary control, influence, or superiority over another within a domestic or home-based context.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69ff6fb9691c819082ee2f3c648b7dc1 |
completed | May 9, 2026, 5:32 p.m. |
Created at: May 3, 2026, 4:09 p.m.