Triple
T30740979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehi |
E782688
|
entity |
| Predicate | leadsGroupFrom |
P170790
|
FINISHED |
| Object | Jerusalem |
—
|
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: Jerusalem | Statement: [Lehi, leadsGroupFrom, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsGroupFrom Context triple: [Lehi, leadsGroupFrom, Jerusalem]
-
A.
leadsGroupTo
Indicates that one entity guides, directs, or is in charge of a group as it moves toward or works to reach a particular destination, goal, or objective.
-
B.
leadsFrom
Indicates that one entity serves as the starting point or origin from which another entity extends, proceeds, or is derived.
-
C.
leadsInto
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
D.
leadSingleFrom
Indicates that one entity serves as the lead single taken from another entity, typically a larger work such as an album or release.
-
E.
helpsLead
Indicates that one entity assists or contributes to another entity’s act of leading or guiding.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:38 p.m.