Triple
T682308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Estates |
E13208
|
entity |
| Predicate | wereComposedOf |
P14960
|
FINISHED |
| Object | principalities |
—
|
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: principalities | Statement: [Imperial Estates, wereComposedOf, principalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereComposedOf Context triple: [Imperial Estates, wereComposedOf, principalities]
-
A.
composedBy
Indicates that one entity is the creator or author of a musical or artistic work associated with another entity.
-
B.
constitutedBy
chosen
Indicates that something is made up of, composed from, or formed by the specified parts or elements.
-
C.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
D.
isCompilationOf
Indicates that one entity is a collected or assembled version made up of multiple other entities.
-
E.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a06f9ee88190a2d757aacd8e3f5b |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.