Triple
T3341703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Man |
E70273
|
entity |
| Predicate | intelligence |
P11340
|
FINISHED |
| Object | genius-level intellect |
—
|
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: genius-level intellect | Statement: [Iron Man, intelligence, genius-level intellect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intelligence Context triple: [Iron Man, intelligence, genius-level intellect]
-
A.
typeOfIntelligence
Indicates that one entity is a specific kind or category of intelligence in relation to another entity.
-
B.
intelligenceLevel
chosen
Indicates the degree or measure of cognitive ability or intelligence attributed to an entity.
-
C.
providesIntelligenceTo
Indicates that one entity supplies information, analysis, or insight that enhances the knowledge or decision-making capability of another entity.
-
D.
intellectualTrend
Indicates a relationship where an idea, movement, or way of thinking is recognized as an intellectual trend influencing thought or discourse.
-
E.
ability
Indicates that an entity has the capacity or power to perform a particular action or achieve a specific outcome.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1ee711481909c0d921f1b5b8562 |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.