Triple
T26176713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF |
E654561
|
entity |
| Predicate | flagRegisterContains |
P4184
|
FINISHED |
| Object | half-carry flag |
—
|
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: half-carry flag | Statement: [AF, flagRegisterContains, half-carry flag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flagRegisterContains Context triple: [AF, flagRegisterContains, half-carry flag]
-
A.
hasRegister
chosen
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
B.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
C.
currentContains
Indicates that one entity presently includes, encloses, or has another entity within its bounds or scope.
-
D.
hasStandardRegister
Indicates that something is expressed or occurs in a standard, neutral, or non-marked linguistic register.
-
E.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6c9b808190812dcb252b9844f2 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:38 p.m.