Triple
T23100266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kryptonian |
E576004
|
entity |
| Predicate | typicalPhysiology |
P58263
|
FINISHED |
| Object | humanoid |
—
|
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: humanoid | Statement: [Kryptonian, typicalPhysiology, humanoid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPhysiology Context triple: [Kryptonian, typicalPhysiology, humanoid]
-
A.
physiology
chosen
Indicates that one entity is related to another through biological or bodily functions, processes, or physiological characteristics.
-
B.
oxygenPhysiology
Indicates the physiological processes, functions, or effects involving oxygen in an organism.
-
C.
circulationSystem
Indicates that one entity functions as the circulatory system of another, responsible for transporting fluids and related substances throughout it.
-
D.
bodyTemperatureRegulation
Indicates how an entity controls or maintains its internal body temperature in response to environmental conditions.
-
E.
vascularSystem
Indicates the relationship in which an entity possesses or is associated with a system of blood vessels that transports blood throughout a body.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de81060819084ab618f05aae583 |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.