Triple
T35839886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbeuf campus |
E1036046
|
entity |
| Predicate | locatedInRegionServed |
P96807
|
FINISHED |
| Object | Elbeuf urban area |
E695936
|
NE 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: Elbeuf urban area | Statement: [Elbeuf campus, locatedInRegionServed, Elbeuf urban area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRegionServed Context triple: [Elbeuf campus, locatedInRegionServed, Elbeuf urban area]
-
A.
locatedInUSRegion
Indicates that one entity is geographically situated within a specified region of the United States.
-
B.
isInhabitedRegionServed
Indicates that a particular inhabited region is provided with services or coverage by a specified entity (such as an organization, facility, or infrastructure).
-
C.
issuerRegionServed
Indicates the geographic region or area that the issuer provides services to or operates within.
-
D.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
E.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
- F. None of above.
Provenance (4 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389c22e5f881909f9747136055e356 |
completed | June 22, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.