Triple
T32924922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalimát |
E842240
|
entity |
| Predicate | hasOrderWithinVahid |
P157316
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Kalimát, hasOrderWithinVahid, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderWithinVahid Context triple: [Kalimát, hasOrderWithinVahid, 6]
-
A.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
establishedWithinOrder
Indicates that one entity was founded, created, or formally established as part of, or under the authority of, a particular order or organizational structure.
-
C.
isOrderIn
chosen
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
-
D.
hasApproximateOrderNumber
Indicates that an entity is associated with a non-exact, estimated, or approximate order number in a sequence or ordering.
-
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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 1:20 a.m.