Triple
T33030470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Monte Vergine |
E845148
|
entity |
| Predicate | isMilitaryOrder |
P175720
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Order of Monte Vergine, isMilitaryOrder, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMilitaryOrder Context triple: [Order of Monte Vergine, isMilitaryOrder, false]
-
A.
hasMilitaryOrder
Indicates that one entity issues, possesses, or is subject to a formal military directive or command from another entity.
-
B.
includesMilitaryOrder
Indicates that one entity contains, encompasses, or formally incorporates a military order within its scope or structure.
-
C.
militaryOrder
Indicates a formal directive or command issued within a military context from a superior authority to subordinates, requiring compliance.
-
D.
isMilitaryCommand
Indicates that one entity holds formal military authority or command over another entity or group.
-
E.
isMilitaryOrderGrade
Indicates that one entity is classified as a specific grade or level within a military order or honor system in relation to another entity.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.