Triple
T8041794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bicha of Balazote |
E187456
|
entity |
| Predicate | humanComponent |
P14071
|
FINISHED |
| Object | male 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: male head | Statement: [Bicha of Balazote, humanComponent, male head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanComponent Context triple: [Bicha of Balazote, humanComponent, male head]
-
A.
isHuman
Indicates that the subject entity possesses the defining characteristics or status of being a human.
-
B.
componentCharacter1
Indicates that one entity is the first (primary) character component or constituent part of another entity.
-
C.
user
Indicates a relationship where an entity actively operates, controls, or interacts with another entity, typically as the primary agent or consumer of its function.
-
D.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
E.
component1
chosen
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f1e98508190a29a7bb5055f8ba0 |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.