Triple
T34690255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makhshirin |
E890871
|
entity |
| Predicate | hasOrderNumberInTohorot |
P60446
|
FINISHED |
| Object | fifth |
—
|
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: fifth | Statement: [Makhshirin, hasOrderNumberInTohorot, fifth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderNumberInTohorot Context triple: [Makhshirin, hasOrderNumberInTohorot, fifth]
-
A.
hasApproximateOrderNumber
Indicates that an entity is associated with a non-exact, estimated, or approximate order number in a sequence or ordering.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
hasMarketingOrderNumber
Indicates that an entity is associated with a specific marketing order number used to identify or track it in marketing or sales processes.
-
D.
orderNumber
chosen
Indicates the unique identifier assigned to a specific order within a transaction or ordering process.
-
E.
isOrderedTo
Indicates that one entity has been formally directed or commanded to perform an action or fulfill a duty by another authority.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 2:05 a.m.