Triple
T17218665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fox |
E417916
|
entity |
| Predicate | secretIdentityStatus |
P100683
|
FINISHED |
| Object | secret |
—
|
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: secret | Statement: [The Fox, secretIdentityStatus, secret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretIdentityStatus Context triple: [The Fox, secretIdentityStatus, secret]
-
A.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
-
B.
knowsSecretIdentityOf
Indicates that one entity is aware of the hidden or private true identity of another entity.
-
C.
hasSuperheroIdentityType
chosen
Indicates the type or category of a superhero identity associated with an entity (e.g., secret, public, dual).
-
D.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
E.
superheroStatus
Indicates that an entity possesses the qualities, role, or designation of being a superhero, such as having heroic abilities, identity, or status.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddb2b148190b3b50572cc285e3d |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.