Triple
T9112246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben |
E218629
|
entity |
| Predicate | canBeUsedAsStandaloneName |
P70064
|
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: [Ben, canBeUsedAsStandaloneName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedAsStandaloneName Context triple: [Ben, canBeUsedAsStandaloneName, true]
-
A.
canBeStandaloneName
Indicates that something is suitable to function independently as a complete, self-contained name without requiring additional qualifiers or context.
-
B.
usedAsIndependentName
Indicates that something is employed as a standalone, self-sufficient name rather than as a dependent or derived form.
-
C.
canBeGivenNameOnItsOwn
chosen
Indicates that something is acceptable or valid to be used as a standalone given name without needing additional components.
-
D.
canBeFormalName
Indicates that something is suitable or valid to be used as a formal or official name.
-
E.
canBeFamilyName
Indicates that something is capable of functioning as a family name or surname in at least one context.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8495c448190b9bb3803fb2dda70 |
completed | April 1, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.