Triple
T24581217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ball |
E608254
|
entity |
| Predicate | replacementCondition |
P64498
|
FINISHED |
| Object | replaced if defective during the 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: replaced if defective during the match | Statement: [The Ball, replacementCondition, replaced if defective during the match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacementCondition Context triple: [The Ball, replacementCondition, replaced if defective during the match]
-
A.
modificationCondition
Indicates the specific circumstances or requirements under which a change or modification to something is permitted, triggered, or becomes applicable.
-
B.
remainderCondition
Indicates that a specified remainder-based condition (such as a modulo constraint) holds between one or more values.
-
C.
cloneCondition
Indicates that one entity is a duplicate or replication of another under the same specified conditions or parameters.
-
D.
replacementOutcome
Indicates the result or consequence that follows from one entity being replaced by another.
-
E.
removalCondition
chosen
Indicates the condition or circumstances under which an entity is removed, deleted, or no longer considered applicable.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a982db00819081038adce05c0b52 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.