Triple
T5240752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Ridge |
E118332
|
entity |
| Predicate | metadataLocation |
P62335
|
FINISHED |
| Object | per-directory record system use fields |
—
|
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: per-directory record system use fields | Statement: [Rock Ridge, metadataLocation, per-directory record system use fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataLocation Context triple: [Rock Ridge, metadataLocation, per-directory record system use fields]
-
A.
documentationLocation
Indicates the place or resource where relevant documentation for an entity can be found.
-
B.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
C.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
D.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
E.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
- F. None of above. chosen
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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b2c50508190b84bab216c30cbfe |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79e9d794819097bb628c603d14af |
completed | March 20, 2026, 4:46 p.m. |
Created at: March 20, 2026, 1:49 p.m.