Triple
T37085695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsunami |
E918279
|
entity |
| Predicate | supportsExpansionBus |
P107285
|
FINISHED |
| Object | PCI |
E699611
|
NE 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: PCI | Statement: [Tsunami, supportsExpansionBus, PCI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExpansionBus Context triple: [Tsunami, supportsExpansionBus, PCI]
-
A.
expansionBus
Indicates a hardware connection through which a device can be attached to or communicate over an expansion bus.
-
B.
hasExpansionInterface
chosen
Indicates that an entity provides or supports an interface through which it can be expanded or extended with additional components or functionality.
-
C.
supportedExpansionOf
Indicates that one entity actively aided, endorsed, or facilitated the growth, extension, or enlargement of another entity or domain.
-
D.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
E.
expansionSlots
Indicates that an entity provides one or more hardware expansion slots available for adding additional components or capabilities.
- F. None of above.
Provenance (4 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdc87fa08190b25f7ab8a395c100 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.