Triple
T10185962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cirrus |
E236907
|
entity |
| Predicate | networkParticipants |
P2434
|
FINISHED |
| Object | banks |
—
|
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: banks | Statement: [Cirrus, networkParticipants, banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkParticipants Context triple: [Cirrus, networkParticipants, banks]
-
A.
notableNetworkParticipants
Indicates that the subject is significantly involved in, or recognized as an important participant within, a particular network.
-
B.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
C.
networkOwner
Indicates that one entity holds ownership or primary control over a particular network.
-
D.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
E.
vowOfParticipants
Indicates that certain participants formally promise or commit themselves to a specified action, condition, or relationship.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded790b488190b1ed4645554873cd |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.