Triple
T32517825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geneva Plan of Action |
E831104
|
entity |
| Predicate | hasNumberOfActionLines |
P4876
|
FINISHED |
| Object | 11 |
—
|
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: 11 | Statement: [Geneva Plan of Action, hasNumberOfActionLines, 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfActionLines Context triple: [Geneva Plan of Action, hasNumberOfActionLines, 11]
-
A.
hasLines
Indicates that one entity contains, is composed of, or is associated with one or more linear elements or line segments.
-
B.
hasNumberOfLines
chosen
Indicates the relationship that specifies how many lines are associated with a given entity.
-
C.
hasDeepLevelLines
Indicates that one entity possesses or exhibits lines that extend to or occur at a deep level within a given structure or context.
-
D.
hasDeFactoLine
Indicates that there exists an unofficial or non-legally recognized boundary or demarcation line functioning in practice between the related entities.
-
E.
hasDominantLines
Indicates that one element in a pair exhibits stronger, more prominent, or controlling linear features relative to the other.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1 a.m.