Triple
T8765631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assembling Objects |
E208331
|
entity |
| Predicate | typicallyScoredBy |
P15617
|
FINISHED |
| Object | number of correctly assembled items |
—
|
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: number of correctly assembled items | Statement: [Assembling Objects, typicallyScoredBy, number of correctly assembled items]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyScoredBy Context triple: [Assembling Objects, typicallyScoredBy, number of correctly assembled items]
-
A.
scoredBy
Indicates that a particular score, point, or result was achieved or obtained by a specific entity.
-
B.
coScoredWith
Indicates that two or more entities received the same score or were evaluated with an identical scoring outcome in a shared context.
-
C.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
D.
isScoreFor
chosen
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
E.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ee850b88190a0294bcbe4045aa3 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.