Triple
T22446032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dart build_runner |
E554863
|
entity |
| Predicate | typicalBuilder |
P56257
|
FINISHED |
| Object | json_serializable |
—
|
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: json_serializable | Statement: [Dart build_runner, typicalBuilder, json_serializable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuilder Context triple: [Dart build_runner, typicalBuilder, json_serializable]
-
A.
builder
Indicates that an entity is responsible for constructing, creating, or assembling another entity.
-
B.
primaryBuilder
Indicates that the subject is the main or lead entity responsible for constructing or creating the object.
-
C.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
D.
typicalComponent
chosen
Indicates that one entity is a standard or representative component or part of another entity.
-
E.
builderModel
Indicates a relationship where one entity serves as the design or construction template (the "builder model") used to create, configure, or generate another entity.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4803908190990280ebd258cb03 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.