Triple
T313611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pursuivant |
E7658
|
entity |
| Predicate | requiresKnowledgeOf |
P6204
|
FINISHED |
| Object | heraldic rules and blazon |
—
|
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: heraldic rules and blazon | Statement: [Pursuivant, requiresKnowledgeOf, heraldic rules and blazon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresKnowledgeOf Context triple: [Pursuivant, requiresKnowledgeOf, heraldic rules and blazon]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiresSkill
chosen
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
-
C.
requiresConfidenceOf
Indicates that one entity can only proceed, function, or be accepted if it has sufficient trust, assurance, or belief in the reliability or correctness of another entity.
-
D.
knowledgeExchange
Indicates a reciprocal sharing or transfer of knowledge, information, or expertise between entities.
-
E.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4bd6a081909bdb57602c7093b4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.