Triple
T2970725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archipelago Exchange |
E80272
|
entity |
| Predicate | offeredFunctionality |
P9404
|
FINISHED |
| Object | electronic order routing |
—
|
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: electronic order routing | Statement: [Archipelago Exchange, offeredFunctionality, electronic order routing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredFunctionality Context triple: [Archipelago Exchange, offeredFunctionality, electronic order routing]
-
A.
providesFunctionalityOf
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
B.
offersFeature
chosen
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
C.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
D.
offeredTechnology
Indicates that one entity has provided or proposed a specific technology to another entity as an option for use, adoption, or consideration.
-
E.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9973ed6881908f11f49ca2e171df |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.