Triple
T8303799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Réseau de l’État |
E194409
|
entity |
| Predicate | hasNetworkOwnership |
P18033
|
FINISHED |
| Object | public |
—
|
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: public | Statement: [Réseau de l’État, hasNetworkOwnership, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNetworkOwnership Context triple: [Réseau de l’État, hasNetworkOwnership, public]
-
A.
networkOwnedStatus
chosen
Indicates whether an entity is owned, controlled, or otherwise possessed by a particular network.
-
B.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
C.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
D.
hasInfrastructureOwner
Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
-
E.
hasNetworkPartner
Indicates that an entity is connected to another entity through a formal or recognized network partnership 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8b9f6081909100d1da8a078616 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.