Triple
T11691119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moor of Freising |
E277869
|
entity |
| Predicate | hasHeadType |
P25789
|
FINISHED |
| Object | Moor's head |
—
|
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: Moor's head | Statement: [Moor of Freising, hasHeadType, Moor's head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadType Context triple: [Moor of Freising, hasHeadType, Moor's head]
-
A.
hasHeadCount
Indicates that an entity is associated with a specific number of individuals, typically representing the size or count of people (or similar units) related to it.
-
B.
headType
chosen
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
C.
hasHeading
Indicates that one entity serves as a heading or title for another entity.
-
D.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
E.
hasHeadPosition
Indicates the specific spatial position or orientation of an entity’s head relative to a reference frame or context.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47a3ddc819098e208611148d15b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.