Triple
T24824566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PETRA III |
E621152
|
entity |
| Predicate | firstUserOperation |
P165287
|
FINISHED |
| Object | around 2009 |
—
|
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: around 2009 | Statement: [PETRA III, firstUserOperation, around 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUserOperation Context triple: [PETRA III, firstUserOperation, around 2009]
-
A.
primaryOperation
Indicates the main or most important operation performed or used by an entity in a given context.
-
B.
firstPassOperation
Indicates that the related action or process occurs during the initial or primary pass of an operation or workflow.
-
C.
firstStepIn
Indicates that one event, action, or process is the initial step in a larger sequence or procedure involving another.
-
D.
firstToAuthorize
Indicates that one entity is the earliest or initial party to grant approval, permission, or authorization for a particular action or arrangement relative to others.
-
E.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
- F. None of above. chosen
Provenance (4 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 18, 2026, 5:05 a.m.