Triple
T35141000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDBNavigator |
E1014700
|
entity |
| Predicate | supportsButton |
P166402
|
FINISHED |
| Object | nbFirst |
—
|
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: nbFirst | Statement: [TDBNavigator, supportsButton, nbFirst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsButton Context triple: [TDBNavigator, supportsButton, nbFirst]
-
A.
buttonSupport
chosen
Indicates that one entity provides structural or functional support for a button associated with another entity.
-
B.
supportsBlock
Indicates that one entity provides structural or functional backing that upholds or stabilizes another entity or block.
-
C.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
-
D.
supportsValue
Indicates that one entity provides justification, evidence, or backing for the truth, relevance, or appropriateness of a particular value associated with another entity.
-
E.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.