Triple
T12900208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EINE |
E308591
|
entity |
| Predicate | extensibilityMechanism |
P11253
|
FINISHED |
| Object | Lisp-based extension language |
—
|
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: Lisp-based extension language | Statement: [EINE, extensibilityMechanism, Lisp-based extension language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extensibilityMechanism Context triple: [EINE, extensibilityMechanism, Lisp-based extension language]
-
A.
extensionMechanism
chosen
Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
-
B.
extensionType
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
-
C.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
D.
architectOfExtension
Indicates that one entity served as the architect responsible for designing an extension to another entity (such as a building or structure).
-
E.
backendExtension
Indicates that one entity functions as an extension or add-on to another entity’s backend system or service.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.