Triple
T8859907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AppleTalk Phase 2 |
E210859
|
entity |
| Predicate | supportsAutoconfiguration |
P31516
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [AppleTalk Phase 2, supportsAutoconfiguration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAutoconfiguration Context triple: [AppleTalk Phase 2, supportsAutoconfiguration, yes]
-
A.
supportsAutoConfiguration
chosen
Indicates that one entity provides or enables automatic configuration capabilities for another entity or process.
-
B.
supportsAutomaticDependencyInstallation
Indicates that an entity is capable of automatically detecting and installing any required dependencies without manual intervention.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
supportsConfigurationFromEnv
Indicates that a component can obtain and apply its configuration settings directly from environment variables.
-
E.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e712d08190bfb1c4ba3acaea90 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.