Triple
T10241210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USD |
E243594
|
entity |
| Predicate | supportsInterchange |
P48616
|
FINISHED |
| Object | DCC tools |
—
|
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: DCC tools | Statement: [USD, supportsInterchange, DCC tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterchange Context triple: [USD, supportsInterchange, DCC tools]
-
A.
hasCrossPlatformInterchange
Indicates that there is a transfer point where passengers can switch between different transportation platforms or modes within the same location.
-
B.
isInterchange
Indicates that two entities can be substituted or exchanged for one another without affecting the relevant system, function, or outcome.
-
C.
isInterchangeWith
Indicates that two entities can be substituted or exchanged for one another without loss of function, value, or compatibility.
-
D.
hasInterchangeType
Indicates that one entity is associated with a specific type or category of interchange (e.g., mode, format, or method of exchange) in relation to another entity.
-
E.
supportedIn
chosen
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:24 a.m.