Triple
T2283871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter Army Airfield |
E51340
|
entity |
| Predicate | hasFAAcode |
P420
|
FINISHED |
| Object | SVN |
E51340
|
NE 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: SVN | Statement: [Hunter Army Airfield, hasFAAcode, SVN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SVN Context triple: [Hunter Army Airfield, hasFAAcode, SVN]
-
A.
SVN
chosen
SVN is the IATA airport code for Hunter Army Airfield, a U.S. military airfield located near Savannah, Georgia.
-
B.
SVN
SVN is the three-letter ISO 3166-1 alpha-3 country code assigned to Slovenia.
-
C.
Subversion
Subversion is a centralized version control system used to manage and track changes to source code and other files in software development projects.
-
D.
Perforce
Perforce is a centralized version control system widely used in game development and large-scale software projects for its performance and robust asset management.
-
E.
Git
Git is a widely used distributed version control system designed to efficiently track changes in source code and support collaborative software development.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc2445f388190af643878145f8249 |
completed | March 7, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae96080548819098ae6c5ab73036f2 |
completed | March 9, 2026, 9:42 a.m. |
Created at: March 4, 2026, 7:48 p.m.