Triple
T30362323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flora McKenzie Robson |
E772320
|
entity |
| Predicate | hasBNFId |
P169116
|
FINISHED |
| Object | 13942477z |
—
|
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: 13942477z | Statement: [Flora McKenzie Robson, hasBNFId, 13942477z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBNFId Context triple: [Flora McKenzie Robson, hasBNFId, 13942477z]
-
A.
hasIbnr
Indicates that one entity possesses or is associated with an incurred-but-not-reported (IBNR) amount, typically referring to estimated liabilities for events that have occurred but have not yet been reported.
-
B.
hasMorphosyntacticBasis
Indicates that one linguistic element’s form or syntactic behavior is grounded in, derived from, or systematically determined by another element’s morphosyntactic properties.
-
C.
hasGrammarFrom
Indicates that one entity derives or uses its grammatical structure or rules from another entity.
-
D.
hasBDDesignation
Indicates that an entity has been assigned a specific BD (Business Development or similar domain-specific) designation or classification.
-
E.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68243b5d8819092d8a0a1261f5fb2 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:58 p.m.