Triple
T24004085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Bridge |
E594323
|
entity |
| Predicate | upperLevelBuiltInYear |
P19392
|
FINISHED |
| Object | 1565 |
—
|
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: 1565 | Statement: [Old Bridge, upperLevelBuiltInYear, 1565]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperLevelBuiltInYear Context triple: [Old Bridge, upperLevelBuiltInYear, 1565]
-
A.
upperLevelCompletionYear
Indicates the year in which an entity completed an upper-level stage of education, training, or qualification.
-
B.
optionalYearBefore
Indicates that one entity may, but does not necessarily, occur or be valid in a year that precedes the year associated with another entity.
-
C.
yearBuilt
chosen
Indicates the specific year in which something (typically a structure or object) was constructed or completed.
-
D.
latestVersionYear
Indicates the calendar year in which the most recent version of an entity (such as a product, document, or software) was released or became available.
-
E.
integratedYear
Indicates the year in which one entity was incorporated into, merged with, or formally added to another entity or system.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d4681fd88190949c5c91d4f94910 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.