Triple
T13889958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahalal |
E333941
|
entity |
| Predicate | hasPlanningInfluence |
P63713
|
FINISHED |
| Object | model for later moshavim |
—
|
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: model for later moshavim | Statement: [Nahalal, hasPlanningInfluence, model for later moshavim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningInfluence Context triple: [Nahalal, hasPlanningInfluence, model for later moshavim]
-
A.
hasPlanningSignificance
Indicates that something holds importance or relevance for planning, decision-making, or future organizational activities.
-
B.
hasPossibleInfluence
chosen
Indicates that one entity may have an effect on, contribute to, or shape the state, behavior, or outcome of another entity, without asserting that this influence is definite or direct.
-
C.
hasPlanningInstrument
Indicates that an entity is associated with, or governed by, a specific planning instrument (such as a plan, policy, or regulatory document) that guides its development or management.
-
D.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
E.
hasPlanningContext
Indicates that an entity is associated with a specific planning-related situation, scope, or set of conditions that frame how it should be interpreted or used.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a3a24881908d81d634622fbbcc |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.