Triple
T7387864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAX+PLUS II |
E170426
|
entity |
| Predicate | supportsDesignEntryMethod |
P203
|
FINISHED |
| Object | schematic entry |
—
|
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: schematic entry | Statement: [MAX+PLUS II, supportsDesignEntryMethod, schematic entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDesignEntryMethod Context triple: [MAX+PLUS II, supportsDesignEntryMethod, schematic entry]
-
A.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
-
B.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f3f5f48190aabe69ba79cbcb93 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.