Triple
T27666719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASF |
E697245
|
entity |
| Predicate | metadataModel |
P152216
|
FINISHED |
| Object | object-based |
—
|
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: object-based | Statement: [ASF, metadataModel, object-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataModel Context triple: [ASF, metadataModel, object-based]
-
A.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
B.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
C.
metaElement
chosen
Indicates that one entity functions as a meta-level descriptor, annotation, or structural element that provides information about another entity rather than being part of its primary content.
-
D.
namespaceModel
Indicates a relationship where a model is defined within, or associated with, a particular namespace or logical grouping.
-
E.
dataTypeModel
Indicates that one entity serves as the data type or schema model that defines the structure or format of 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:38 p.m.