Triple
T6235503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protector RG1 |
E139467
|
entity |
| Predicate | serviceEntryPlannedFor |
P62980
|
FINISHED |
| Object | 2020s |
—
|
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: 2020s | Statement: [Protector RG1, serviceEntryPlannedFor, 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryPlannedFor Context triple: [Protector RG1, serviceEntryPlannedFor, 2020s]
-
A.
plannedService
chosen
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
B.
plannedServiceType
Indicates the category or kind of service that has been scheduled or planned to be provided.
-
C.
serviceEntryStatus
Indicates the current state or condition of a service entry within a process or system (e.g., whether it is active, pending, completed, or otherwise classified).
-
D.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used 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_69c008b0e7ac8190808a59573ee646f3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062f236608190997e77b41095883f |
completed | March 22, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69c05601de6481909d0880048fd7b49a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.