Triple
T12932827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Midas |
E309424
|
entity |
| Predicate | secretRevealedBy |
P30306
|
FINISHED |
| Object | his barber |
—
|
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: his barber | Statement: [King Midas, secretRevealedBy, his barber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretRevealedBy Context triple: [King Midas, secretRevealedBy, his barber]
-
A.
revealedSecretOf
chosen
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
B.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
-
C.
identityRevealedIn
Indicates that an entity’s true identity becomes known or disclosed within a specified context, source, or situation.
-
D.
isRevealedTo
Indicates that previously hidden or unknown information becomes known to a specific entity or group.
-
E.
knowsSecret
Indicates that one entity is aware of confidential or hidden information about another entity or situation.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.