Triple
T23298647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahava Rabba mode |
E590240
|
entity |
| Predicate | commonKeyExample |
P80279
|
FINISHED |
| Object | D Ahava Rabba |
—
|
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: D Ahava Rabba | Statement: [Ahava Rabba mode, commonKeyExample, D Ahava Rabba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonKeyExample Context triple: [Ahava Rabba mode, commonKeyExample, D Ahava Rabba]
-
A.
keyExample
chosen
Indicates that something serves as a representative or illustrative instance of a key concept, feature, or case.
-
B.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
C.
centralExample
Indicates that one entity serves as the primary or most representative example of another entity or concept.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
commonCompoundExample
Indicates that one entity is a typical or illustrative example of a chemical compound associated with 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d133448190bf350a9f51c1531c |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:03 p.m.