Triple
T15741649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic Lām |
E381615
|
entity |
| Predicate | joinsOnRight |
P44437
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Arabic Lām, joinsOnRight, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinsOnRight Context triple: [Arabic Lām, joinsOnRight, true]
-
A.
joins
Indicates that one entity becomes a member or part of another entity, typically by entering into an organization, group, or association.
-
B.
joinsBefore
Indicates that one entity becomes a member or participant in a group, process, or activity earlier in time than another entity.
-
C.
hasRightJoiningForm
chosen
Indicates that one element connects or attaches to the right side of another element in a specific form or configuration.
-
D.
associatedWithRight
Indicates a relationship in which an entity is connected to, linked with, or related to something characterized as "right" (such as a right-hand side, a legal right, or a correct option), depending on the domain context.
-
E.
preUnionRight
Indicates that the subject entity existed or held a status immediately before a union or merging event involving the object 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.