Triple
T1758991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plymouth Rock |
E38612
|
entity |
| Predicate | APAClass |
P31413
|
FINISHED |
| Object | American class |
—
|
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: American class | Statement: [Plymouth Rock, APAClass, American class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: APAClass Context triple: [Plymouth Rock, APAClass, American class]
-
A.
infraclass
Indicates a taxonomic relationship where one entity is classified as an infraclass, a rank below subclass and above order, within the biological hierarchy of another.
-
B.
academyClass
Indicates that an entity is a class, course, or instructional grouping offered within an academy or educational institution.
-
C.
hasApse
Indicates that a structure or building possesses an apse, typically a semicircular or polygonal recess, as one of its architectural features.
-
D.
areaComponent
Indicates that one area is a constituent or sub-area that forms part of a larger area.
-
E.
includesInfraclass
Indicates that one entity is classified as belonging to a specific infraclass within a taxonomic hierarchy.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab173830a481908b67928f16f5d999 |
completed | March 6, 2026, 6:04 p.m. |
Created at: March 4, 2026, 7:31 p.m.