Triple
T27582305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VL-Bus |
E699613
|
entity |
| Predicate | performanceAdvantageOver |
P7339
|
FINISHED |
| Object | ISA |
—
|
NE NERFINISHED |
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: ISA | Statement: [VL-Bus, performanceAdvantageOver, ISA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceAdvantageOver Context triple: [VL-Bus, performanceAdvantageOver, ISA]
-
A.
notableAdvantage
chosen
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
B.
advantageOverPhysical
Indicates that something possesses a benefit or superiority when compared to a physical or tangible counterpart.
-
C.
competitiveEffect
Indicates that one entity’s actions or presence influence another entity’s ability to compete, typically by enhancing or diminishing its competitive position or performance.
-
D.
performanceDescribedAs
Indicates that a performance is characterized or labeled using a particular description or evaluative term.
-
E.
performanceAs
Indicates that one entity serves in a particular role, character, or capacity within a performance or presentation involving 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 27, 2026, 2:03 p.m.