Triple
T7896701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C# lexical structure |
E183357
|
entity |
| Predicate | groupsCharactersInto |
P11608
|
FINISHED |
| Object | identifiers |
—
|
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: identifiers | Statement: [C# lexical structure, groupsCharactersInto, identifiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupsCharactersInto Context triple: [C# lexical structure, groupsCharactersInto, identifiers]
-
A.
groupCharacterization
Indicates how a group as a whole is described or characterized in terms of its shared properties, traits, or defining features.
-
B.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
C.
notableCharacterGroup
Indicates that a group of characters is especially prominent, significant, or noteworthy within a given context or work.
-
D.
letterGroups
chosen
Indicates that entities are organized or associated into specific groups based on letters or letter-based criteria.
-
E.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a187a0081909a0c0822c6dab1da |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.