Triple
T35815345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed Boone |
E1035343
|
entity |
| Predicate | actuallyKnows |
P22660
|
FINISHED |
| Object | Judy Boone is alive |
—
|
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: Judy Boone is alive | Statement: [Ed Boone, actuallyKnows, Judy Boone is alive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actuallyKnows Context triple: [Ed Boone, actuallyKnows, Judy Boone is alive]
-
A.
knows
chosen
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
knownToBe
Indicates that one entity is recognized or acknowledged as being a certain way, having a certain property, or fitting a particular description by others.
-
D.
actuallyDoes
Indicates that an entity truly performs or carries out a specified action or behavior, as opposed to merely being expected, claimed, or assumed to do so.
-
E.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
- 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_69f76e1762408190b885a8456862e372 |
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.