Triple
T18300657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEC API |
E438348
|
entity |
| Predicate | supportsEnvironmentType |
P11908
|
FINISHED |
| Object | board games |
—
|
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: board games | Statement: [AEC API, supportsEnvironmentType, board games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEnvironmentType Context triple: [AEC API, supportsEnvironmentType, board games]
-
A.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
-
B.
supportsEnvironment
chosen
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsEnvironmentMapping
Indicates that one entity provides or enables environment mapping functionality for another entity or context.
-
E.
supportsHostType
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified host 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017f63dc819083a675d570620f2f |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.