Triple
T4678036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salford Quays |
E103728
|
entity |
| Predicate | hasDevelopmentStart |
P10779
|
FINISHED |
| Object | late 1980s |
—
|
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: late 1980s | Statement: [Salford Quays, hasDevelopmentStart, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevelopmentStart Context triple: [Salford Quays, hasDevelopmentStart, late 1980s]
-
A.
hasDevelopmentType
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
B.
developmentBegan
chosen
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
C.
hasDevelopmentSystem
Indicates that one entity possesses, uses, or is associated with a particular system, platform, or environment used for development activities.
-
D.
developedAt
Indicates the place or location where something was created, built, or developed.
-
E.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.