Triple
T7398671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bob |
E170689
|
entity |
| Predicate | isStandaloneName |
P67171
|
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: [Bob, isStandaloneName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandaloneName Context triple: [Bob, isStandaloneName, true]
-
A.
canBeStandaloneName
chosen
Indicates that something is suitable to function independently as a complete, self-contained name without requiring additional qualifiers or context.
-
B.
isUniqueWithinStandard
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
-
C.
isStandOf
Indicates that one entity serves as the Stand (a supernatural or personified power) belonging to or associated with another entity.
-
D.
isAmbiguousName
Indicates that a name can refer to multiple distinct entities or interpretations, making its reference unclear without additional context.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f24c1c208190a3d11e816888760d |
completed | March 27, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.