Triple
T29168164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZZ method |
E739378
|
entity |
| Predicate | typicalMoveCount |
P32659
|
FINISHED |
| Object | low 50s for advanced solvers |
—
|
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: low 50s for advanced solvers | Statement: [ZZ method, typicalMoveCount, low 50s for advanced solvers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMoveCount Context triple: [ZZ method, typicalMoveCount, low 50s for advanced solvers]
-
A.
numberOfMovements
chosen
Indicates the total count of distinct movements or motion events associated with the given entity or context.
-
B.
typicalMovementCountPerQuintet
Indicates the usual number of movements contained within a five-part (quintet) grouping.
-
C.
typicalAnalysisDepth
Indicates the usual or characteristic level of detail or depth at which an analysis is performed or interpreted between entities.
-
D.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
E.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a018c6b7178819097d5450a1e3c2408 |
completed | May 11, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_6a018a4f741c8190babe721a908e2f5e |
completed | May 11, 2026, 7:50 a.m. |
Created at: April 28, 2026, 11:51 a.m.