Triple
T28479391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Directory of Spain |
E720648
|
entity |
| Predicate | hasCabinetType |
P21145
|
FINISHED |
| Object | military directory |
—
|
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: military directory | Statement: [Military Directory of Spain, hasCabinetType, military directory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabinetType Context triple: [Military Directory of Spain, hasCabinetType, military directory]
-
A.
hasCabinet
Indicates that one entity possesses, includes, or is equipped with a cabinet associated with it.
-
B.
cabinetType
chosen
Indicates the specific kind or category of cabinet associated with an entity.
-
C.
hasCabinetName
Indicates that an entity is associated with a specific cabinet by its name.
-
D.
isInCabinet
Indicates that one entity serves as a member of the governing cabinet associated with another entity (such as a government or administration).
-
E.
cabinetRequires
Indicates that a particular cabinet depends on or needs another specified item, condition, or component to be present or satisfied.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 2:54 a.m.