Triple
T17584587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Lamb |
E428288
|
entity |
| Predicate | mayRequireDisambiguation |
P70903
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [John Lamb, mayRequireDisambiguation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayRequireDisambiguation Context triple: [John Lamb, mayRequireDisambiguation, true]
-
A.
supportsDisambiguationOf
Indicates that one entity helps clarify or distinguish the correct meaning or identity of another entity among multiple possible interpretations.
-
B.
hasDisambiguationNote
chosen
Indicates that there is an explanatory note used to distinguish this entity or term from other entities or terms with similar or identical names.
-
C.
mayRequest
Indicates that one entity is permitted or authorized to make a request to another entity or for a particular resource or action.
-
D.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
E.
mayRequireAdditionalStep
Indicates that performing one action, process, or condition can necessitate an extra step beyond the standard or initial sequence.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d113b08190975506f3558c1eca |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.