Triple
T31248740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | לבן הארמי |
E796756
|
entity |
| Predicate | מופיע_בביטוי |
P118237
|
FINISHED |
| Object | ארמי אובד אבי |
—
|
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: ארמי אובד אבי | Statement: [לבן הארמי, מופיע_בביטוי, ארמי אובד אבי]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מופיע_בביטוי Context triple: [לבן הארמי, מופיע_בביטוי, ארמי אובד אבי]
-
A.
appearsInContextWith
chosen
Indicates that two entities are observed or used together within the same situational, textual, or usage context.
-
B.
hasExpressionIn
Indicates that one entity is manifested, represented, or realized within another entity, typically as a specific form, version, or expression.
-
C.
arisesIn
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
-
D.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
-
E.
usedInExpression
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:11 p.m.