Triple
T37503792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battlemode |
E932038
|
entity |
| Predicate | supportsPrivateMatches |
P205933
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Battlemode, supportsPrivateMatches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPrivateMatches Context triple: [Battlemode, supportsPrivateMatches, yes]
-
A.
supportsPartialMatch
Indicates that the relationship or operation allows matching based on a subset or portion of the target criteria rather than requiring a complete or exact match.
-
B.
supportsMultipleMatches
Indicates that the relationship or operation can involve or return more than one matching counterpart rather than being limited to a single match.
-
C.
supportsMatching
Indicates that one entity provides assistance, resources, or functionality that aligns with or complements another entity’s specific requirements or characteristics.
-
D.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
E.
includesMatchesFrom
Indicates that one entity contains or aggregates matches or matching results that originate from another source or 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.