Triple
T22584562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R₣ |
E564752
|
entity |
| Predicate | placementRelativeToNumber |
P139040
|
FINISHED |
| Object | before amount |
—
|
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: before amount | Statement: [R₣, placementRelativeToNumber, before amount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placementRelativeToNumber Context triple: [R₣, placementRelativeToNumber, before amount]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
positionOnNumbers
chosen
Indicates a relationship where one entity occupies a specific numerical position or rank relative to others in an ordered sequence of numbers.
-
C.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
D.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
E.
isNumberedRelativeTo
Indicates that one entity’s numbering or ordinal position is defined or interpreted in relation 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615b4fa08190a8d2d66e01db429f |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:44 p.m.