Triple
T6171615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Public Library main branch |
E137712
|
entity |
| Predicate | hasTeenSection |
P69202
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cambridge Public Library main branch, hasTeenSection, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeenSection Context triple: [Cambridge Public Library main branch, hasTeenSection, true]
-
A.
hasSeniorSection
Indicates that an entity includes or is associated with a designated section or area specifically intended for seniors.
-
B.
hasLowerAge
Indicates that one entity is younger in age than another entity.
-
C.
hasSept
Indicates that one entity possesses, contains, or is associated with a sept (a subdivision or clan group) in relation to another entity.
-
D.
hasJuniorStatus
Indicates that one entity holds a lower, subordinate, or less senior status relative to another entity within a defined hierarchy or context.
-
E.
hasSect
Indicates that an entity includes, contains, or is associated with a particular sect or subgroup within a larger religious, ideological, or organizational context.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d910c3c8190ae6af548259295ff |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.