Triple
T26176698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF |
E654561
|
entity |
| Predicate | alternateRegisterPair |
P161683
|
FINISHED |
| Object | AF' |
—
|
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: AF' | Statement: [AF, alternateRegisterPair, AF']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternateRegisterPair Context triple: [AF, alternateRegisterPair, AF']
-
A.
registerPair
Indicates that two entities are formally recorded or linked together as a pair within a system or registry.
-
B.
canPairRegistersFor
Indicates that two registers are compatible and allowed to be paired together for a combined or coordinated operation.
-
C.
relatedRegister
Indicates a relationship where one entity is associated with, linked to, or corresponds to a particular register or record in a system.
-
D.
relatedRegistry
Indicates that one registry has an association or linkage to another registry.
-
E.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 26, 2026, 8:38 p.m.