Triple
T7938800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud Native Computing Foundation |
E184342
|
entity |
| Predicate | hostsProject |
P2592
|
FINISHED |
| Object | NATS |
E183381
|
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: NATS | Statement: [Cloud Native Computing Foundation, hostsProject, NATS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NATS Context triple: [Cloud Native Computing Foundation, hostsProject, NATS]
-
A.
NATS
chosen
NATS is a high-performance, cloud-native messaging system used for building scalable, distributed applications and microservices.
-
B.
Pegas Fly
Pegas Fly is a Russian airline that operates domestic and international passenger flights, using Sheremetyevo International Airport as one of its main bases.
-
C.
Canair
Canair was a Spanish regional airline that operated inter-island flights in the Canary Islands.
-
D.
Volans
Volans is a small southern sky constellation representing a flying fish, located near the Large Magellanic Cloud.
-
E.
Equair
Equair is an Ecuadorian airline that operated domestic passenger flights, notably serving routes from Guayaquil and Quito.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3af0a2048190838d1aeda59fda0b |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5c0e868481908748d340244ea8ea |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:08 p.m.