Triple
T25036354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Official Code of Georgia Annotated |
E626986
|
entity |
| Predicate | isOfficialCodeOf |
P9567
|
FINISHED |
| Object | Georgia |
—
|
NE NERFINISHED |
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: Georgia | Statement: [Official Code of Georgia Annotated, isOfficialCodeOf, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficialCodeOf Context triple: [Official Code of Georgia Annotated, isOfficialCodeOf, Georgia]
-
A.
isOfficialCodeFor
chosen
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
B.
isOfficialOrganOf
Indicates that one entity serves as the formally designated organ, body, or institutional component of another entity within an official or legal structure.
-
C.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
D.
isOfficialOfficeOf
Indicates that one entity serves as the formally recognized office or headquarters associated with another entity.
-
E.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4530674d88190a3516bbd64234111 |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:08 a.m.