Triple
T15518087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albanian Revolt of 1912 |
E368883
|
entity |
| Predicate | hasDemand |
P6501
|
FINISHED |
| Object | autonomous Albanian vilayet |
—
|
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: autonomous Albanian vilayet | Statement: [Albanian Revolt of 1912, hasDemand, autonomous Albanian vilayet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemand Context triple: [Albanian Revolt of 1912, hasDemand, autonomous Albanian vilayet]
-
A.
promptedDemandFor
Indicates that one entity’s action or occurrence caused an increase in demand for another entity.
-
B.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
C.
dialogRequirement
Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
-
D.
demanded
chosen
Indicates that one entity forcefully or insistently requested something from another entity.
-
E.
returnRequirement
Indicates that an entity is obligated or expected to be sent back or restored to its original source or owner.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e040343d9c8190a7d1f197c108bd9d |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:03 a.m.