Triple
T5923837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pub.dev |
E131756
|
entity |
| Predicate | urlFormat |
P49348
|
FINISHED |
| Object | https://pub.dev/packages/{package_name} |
—
|
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: https://pub.dev/packages/{package_name} | Statement: [pub.dev, urlFormat, https://pub.dev/packages/{package_name}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urlFormat
Context triple: [pub.dev, urlFormat, https://pub.dev/packages/{package_name}]
-
A.
URLPattern
chosen
Indicates that a resource or endpoint is identified or matched by a specific structured web address pattern.
-
B.
coordinateFormat
Indicates the specific representation or notation used to express a set of coordinates.
-
C.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
D.
formerUrl
Indicates that one entity was previously identified or accessible via the URL represented by the other entity, but that URL is no longer current.
-
E.
routeNumberFormat
Indicates how the identifying number or code for a route is structured or formatted.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.