Triple
T4248551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip the Tetrarch |
E95786
|
entity |
| Predicate | administrativeStyle |
P40450
|
FINISHED |
| Object | mild |
—
|
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: mild | Statement: [Philip the Tetrarch, administrativeStyle, mild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeStyle Context triple: [Philip the Tetrarch, administrativeStyle, mild]
-
A.
officeHolderStyle
Indicates the formal title, manner of address, or stylistic designation used for a person holding a particular office or position.
-
B.
governingStyleAssociatedWith
chosen
Indicates a relationship where a particular governing style, method, or approach is linked or attributed to a specific entity (such as a leader, regime, or organization).
-
C.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
D.
administrativeFeature
Indicates that one entity serves as an administrative or governance-related feature, function, or attribute associated with another entity.
-
E.
patronageStyle
Indicates the manner or characteristic way in which support, sponsorship, or patronage is provided in a relationship.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9cb71481909b4baa370193148f |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.