Triple
T31504055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arms of the House of Leiningen |
E803766
|
entity |
| Predicate | governsUse |
P3020
|
FINISHED |
| Object | rules of heraldry |
—
|
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: rules of heraldry | Statement: [arms of the House of Leiningen, governsUse, rules of heraldry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsUse Context triple: [arms of the House of Leiningen, governsUse, rules of heraldry]
-
A.
governedDuringUseBy
Indicates that an entity is subject to the authority, control, or regulatory power of another entity specifically during the period in which it is being used.
-
B.
regulatesUse
chosen
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
C.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
D.
governedForPurpose
Indicates that one entity exercises governance or control over another specifically to achieve a particular purpose or intended function.
-
E.
governsRightsOf
Indicates that one entity has legal or authoritative control over determining, defining, or regulating the rights of another entity.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
Created at: April 30, 2026, 9:46 p.m.