Triple
T35843546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Kandor |
E1036149
|
entity |
| Predicate | restorationAttemptsBy |
P43649
|
FINISHED |
| Object | Superman |
—
|
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: Superman | Statement: [City of Kandor, restorationAttemptsBy, Superman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restorationAttemptsBy Context triple: [City of Kandor, restorationAttemptsBy, Superman]
-
A.
restorationAttemptOutcome
Indicates the result or status achieved from an attempt to restore something to a previous or desired condition.
-
B.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
-
C.
completionAttemptsBy
Indicates that a specific entity’s completion attempts are attributed to or performed by another entity.
-
D.
attemptedRestoration
chosen
Indicates an action where an entity makes an effort to restore or return another entity to a previous or desired state, condition, or form, regardless of whether the restoration succeeds.
-
E.
attemptNumber
Indicates the specific ordinal count of attempts made for a given action or process.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.