Triple
T32636594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotan |
E834359
|
entity |
| Predicate | headCount |
P54817
|
FINISHED |
| Object | seven heads |
—
|
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: seven heads | Statement: [Lotan, headCount, seven heads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headCount Context triple: [Lotan, headCount, seven heads]
-
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.
numberOfHeads
chosen
Indicates the count of heads that an entity possesses.
-
C.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
D.
headType
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).
-
E.
headDisplayedIn
Indicates that a person’s head (or head representation) is shown or depicted within a particular medium, context, or location.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c775d6188190b236fc4f89a11b61 |
completed | May 3, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:07 a.m.