Triple
T35208170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dis-arm-her |
E1016596
|
entity |
| Predicate | canEndMatchType |
P30656
|
FINISHED |
| Object | singles match |
—
|
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: singles match | Statement: [Dis-arm-her, canEndMatchType, singles match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEndMatchType Context triple: [Dis-arm-her, canEndMatchType, singles match]
-
A.
canEndOn
Indicates that one entity is allowed or able to terminate, conclude, or finish with another specified entity or condition.
-
B.
usesMatchType
Indicates that one entity applies or operates according to a specific type or category of matching criteria defined by another entity.
-
C.
matchesType
Indicates that one entity has the same or a compatible type as another entity according to a defined type system or classification.
-
D.
finalMatchType
chosen
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
E.
includesMatchType
Indicates that one entity’s set or collection contains an element with a specified type of match (e.g., exact, partial, or pattern-based) to another entity.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.