Triple
T26392080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amoukar |
E663438
|
entity |
| Predicate | leadsExpeditionWith |
P160494
|
FINISHED |
| Object | Naoh |
—
|
NE NERFINISHED |
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: Naoh | Statement: [Amoukar, leadsExpeditionWith, Naoh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsExpeditionWith Context triple: [Amoukar, leadsExpeditionWith, Naoh]
-
A.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
B.
leads
Indicates having primary responsibility for directing, guiding, or managing another entity or group toward a goal or outcome.
-
C.
leadsAstray
Indicates that one entity causes another entity to deviate from a correct, moral, or intended path or course of action.
-
D.
helpsLead
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
-
E.
leadType
Indicates the specific category or classification of a lead within a lead management or sales context.
- F. None of above. chosen
Provenance (4 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610c024f081908237794984538566 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:26 p.m.