Triple
T30348542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurren Lagann (combined mecha) |
E771928
|
entity |
| Predicate | headFrom |
P169412
|
FINISHED |
| Object | Lagann |
—
|
NE NERFINISHED |
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: Lagann | Statement: [Gurren Lagann (combined mecha), headFrom, Lagann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headFrom Context triple: [Gurren Lagann (combined mecha), headFrom, Lagann]
-
A.
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).
-
B.
headGivesRiseTo
Indicates that one entity (the head) is the source or origin from which another entity arises, develops, or is produced.
-
C.
headLocation
Indicates the spatial position or place where an entity’s head is located.
-
D.
headDescription
Indicates that one entity serves as a textual or semantic description of the head (primary) entity in the relationship.
-
E.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
- F. None of above. chosen
Provenance (4 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6820a250c8190ba7afa43f6f55c46 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:56 p.m.