Triple
T6737889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LS |
E154001
|
entity |
| Predicate | trimHierarchyRole |
P72666
|
FINISHED |
| Object | entry point to model range |
—
|
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: entry point to model range | Statement: [LS, trimHierarchyRole, entry point to model range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trimHierarchyRole Context triple: [LS, trimHierarchyRole, entry point to model range]
-
A.
ordinationRole
Indicates the specific religious or ceremonial office, function, or capacity in which an entity is formally ordained.
-
B.
orderHierarchy
Indicates a hierarchical ordering relationship where one entity is positioned above or below another in a structured sequence or chain of command.
-
C.
redefinedRoleOf
Indicates that one entity has changed, updated, or newly specified the function, responsibilities, or position of another entity.
-
D.
catalogRole
Indicates that an entity holds a specific functional role or responsibility within the context of a catalog or cataloging system.
-
E.
titleHierarchy
Indicates a hierarchical relationship between titles, where one title is ranked above or below another in an ordered structure.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1850a288190aa7e647fefbb0ede |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d14e18d481908aaac34897c650f1 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:10 p.m.