Triple
T30634860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cole Sear |
E779810
|
entity |
| Predicate | firstConfidesSecretTo |
P33486
|
FINISHED |
| Object | Malcolm Crowe |
E498045
|
NE 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: Malcolm Crowe | Statement: [Cole Sear, firstConfidesSecretTo, Malcolm Crowe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstConfidesSecretTo Context triple: [Cole Sear, firstConfidesSecretTo, Malcolm Crowe]
-
A.
confidantOf
Indicates a relationship in which one entity is trusted by another to receive and keep personal, private, or sensitive information.
-
B.
confidesIn
chosen
Indicates that one entity shares private, sensitive, or personal information or feelings with another entity in trust.
-
C.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
D.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
E.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
- F. None of above.
Provenance (4 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0309a4e4d481908a6070b40d507aae |
completed | May 12, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870eb21b481908b1928198dbd3433 |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_6a03091ac1008190bf50357364d4e9e4 |
completed | May 12, 2026, 11:03 a.m. |
Created at: April 29, 2026, 8:28 p.m.