Triple
T27737252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.MethodAttributes |
E697558
|
entity |
| Predicate | isFlagEnum |
P163167
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [System.Reflection.MethodAttributes, isFlagEnum, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFlagEnum Context triple: [System.Reflection.MethodAttributes, isFlagEnum, true]
-
A.
isFlagsEnum
chosen
Indicates that an enumeration type is intended to be used as a bit field, where its values can be combined using bitwise operations to represent multiple flags simultaneously.
-
B.
isEnum
Indicates that something is classified as an enumeration type, representing a fixed set of discrete, named values.
-
C.
isStateFlagOf
Indicates that one entity is the official state flag representing the specified state or region.
-
D.
definesFlag
Indicates that one entity specifies or establishes a particular flag or boolean indicator used by another entity or process.
-
E.
hasFlagOrSymbol
Indicates that an entity possesses, uses, or is associated with a particular flag or symbolic emblem.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 3:13 p.m.