Triple
T28390193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allendale Campus |
E719131
|
entity |
| Predicate | hasTechnologyFacilities |
P12416
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Allendale Campus, hasTechnologyFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTechnologyFacilities Context triple: [Allendale Campus, hasTechnologyFacilities, yes]
-
A.
hasTechnologySystem
Indicates that one entity possesses, utilizes, or is supported by a particular technology system.
-
B.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
hasCoreFacility
Indicates that an entity possesses, hosts, or is equipped with a central, shared facility that supports key operations or services.
-
D.
hasMediaFacilities
Indicates that an entity possesses or provides access to media-related infrastructure or equipment (such as studios, recording, broadcasting, or production facilities).
-
E.
hasFacilityFunction
Indicates that a facility performs, supports, or is designated for a particular function or operational role.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 1:13 a.m.