Triple
T5376098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Museum of Natural History |
E108962
|
entity |
| Predicate | collectionSubject |
P17067
|
FINISHED |
| Object | regional flora |
—
|
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: regional flora | Statement: [Georgia Museum of Natural History, collectionSubject, regional flora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionSubject Context triple: [Georgia Museum of Natural History, collectionSubject, regional flora]
-
A.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
B.
subjectOfCatalog
Indicates that something is the primary focus or entry described within a catalog or cataloging record.
-
C.
collectionRole
Indicates the specific function, responsibility, or position an entity holds within a collection or grouped set of items.
-
D.
collectionScope
chosen
Indicates the extent, boundaries, or range over which a collection (such as a set of items, data, or resources) is defined or intended to apply.
-
E.
dataSubjects
Indicates a relationship where certain individuals or entities are the subjects about whom data is collected, processed, or referenced.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.