Triple
T3384607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strijp |
E71265
|
entity |
| Predicate | formerPrimaryFunction |
P5925
|
FINISHED |
| Object | industrial area |
—
|
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: industrial area | Statement: [Strijp, formerPrimaryFunction, industrial area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPrimaryFunction Context triple: [Strijp, formerPrimaryFunction, industrial area]
-
A.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
formerFunction
chosen
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
C.
primaryFunctionContext
Indicates the main situational or operational context in which a function, role, or process is primarily intended to be used or performed.
-
D.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
E.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5ee5e188190912dcea494a12038 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:14 p.m.