Triple
T14454164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Analytics |
E358409
|
entity |
| Predicate | standardPropertiesStoppedProcessingDate |
P101820
|
FINISHED |
| Object | 2023-07-01 |
—
|
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: 2023-07-01 | Statement: [Universal Analytics, standardPropertiesStoppedProcessingDate, 2023-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardPropertiesStoppedProcessingDate Context triple: [Universal Analytics, standardPropertiesStoppedProcessingDate, 2023-07-01]
-
A.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
B.
cessationDate
chosen
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
-
C.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
D.
lastProcessingEnded
Indicates that the most recent processing activity or operation for the entity has come to an end.
-
E.
dateOfSuppression
Indicates the specific date on which something (such as information, a record, or a right) was formally suppressed, withheld, or made inactive.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a8bf088190abf5fd4f646b8c62 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.