Triple
T32234871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufe |
E823440
|
entity |
| Predicate | hasReportingNameType |
—
|
GENERATED |
| Object | Allied reporting name |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReportingNameType Context triple: [Rufe, hasReportingNameType, Allied reporting name]
-
A.
supportsNameType
Indicates that one entity is capable of handling, recognizing, or being associated with a particular type or category of name.
-
B.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
C.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
D.
hasRegistrationType
Indicates that an entity is associated with a specific category or type of registration it holds or requires.
-
E.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
- F. None of above. chosen
Provenance (1 batch)
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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:39 a.m.