Triple
T3705871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gimel |
E80890
|
entity |
| Predicate | hasTraditionalOrderPrecededBy |
P25144
|
FINISHED |
| Object | Bet |
—
|
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: Bet | Statement: [Gimel, hasTraditionalOrderPrecededBy, Bet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalOrderPrecededBy Context triple: [Gimel, hasTraditionalOrderPrecededBy, Bet]
-
A.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
B.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
-
C.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
D.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
-
E.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc54ce1788190ac000793cbdaba48 |
completed | March 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.