Triple
T9440650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Power |
E227634
|
entity |
| Predicate | hasDisambiguationNeedIn |
P38403
|
FINISHED |
| Object | databases |
—
|
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: databases | Statement: [John Power, hasDisambiguationNeedIn, databases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisambiguationNeedIn Context triple: [John Power, hasDisambiguationNeedIn, databases]
-
A.
hasDisambiguationNote
Indicates that there is an explanatory note used to distinguish this entity or term from other entities or terms with similar or identical names.
-
B.
hasDisambiguationPage
chosen
Indicates that there exists a disambiguation page used to distinguish between multiple entities or meanings associated with the same term.
-
C.
supportsDisambiguationOf
Indicates that one entity helps clarify or distinguish the correct meaning or identity of another entity among multiple possible interpretations.
-
D.
languageAmbiguity
Indicates that the meaning, interpretation, or reference of a linguistic expression is unclear or can be understood in multiple ways.
-
E.
hasAmbiguousEnding
Indicates that the event, story, or situation concludes in a way that is open to multiple interpretations or lacks a clear, definitive resolution.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ee36f908190826994db91b18466 |
completed | April 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:50 p.m.