Triple
T14454159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Analytics |
E358409
|
entity |
| Predicate | propertyIDFormat |
P78161
|
FINISHED |
| Object | UA-XXXXXX-Y |
—
|
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: UA-XXXXXX-Y | Statement: [Universal Analytics, propertyIDFormat, UA-XXXXXX-Y]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyIDFormat Context triple: [Universal Analytics, propertyIDFormat, UA-XXXXXX-Y]
-
A.
identificationNumberFormat
chosen
Indicates the specific structural pattern or rules that an identification number must follow.
-
B.
propertyType_rid
Indicates that an entity is associated with a specific property type identified by a unique resource identifier (RID).
-
C.
protocolIdentifierFormat
Indicates how a protocol’s identifier is structured or formatted.
-
D.
propertyForm
Indicates the specific form, type, or configuration that a property takes within a given context or system.
-
E.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
- 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.