Triple
T7665521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flyweight |
E173613
|
entity |
| Predicate | commonExample |
P8562
|
FINISHED |
| Object | character objects in text editors |
—
|
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: character objects in text editors | Statement: [Flyweight, commonExample, character objects in text editors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonExample Context triple: [Flyweight, commonExample, character objects in text editors]
-
A.
commonConcept
Indicates that two or more entities share the same underlying idea, notion, or conceptual meaning.
-
B.
toolUseExamples
chosen
Indicates that one entity provides example instances or demonstrations of how a particular tool is or can be used by another entity.
-
C.
usedAsExampleIn
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
-
D.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
E.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.