Triple
T8823042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blender |
E209950
|
entity |
| Predicate | supportsFormat |
P203
|
FINISHED |
| Object | FBX |
E630488
|
NE 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: FBX | Statement: [Blender, supportsFormat, FBX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FBX Context triple: [Blender, supportsFormat, FBX]
-
A.
FBX
chosen
FBX is a widely used 3D asset exchange file format that supports complex geometry, materials, animation, and scene data across various graphics and game development applications.
-
B.
FBB
FBB is the operating company responsible for managing Berlin Brandenburg Airport and related airport facilities in the Berlin region.
-
C.
FBO
FBO, short for Film Booking Offices of America, was a 1920s American film distribution and production company that later became part of RKO Pictures.
-
D.
Modo
Modo is a Swedish professional ice hockey club known for developing numerous NHL players and competing in the country’s top leagues.
-
E.
Universal Scene Description
Universal Scene Description (USD) is an open-source 3D scene description and interchange framework developed by Pixar, widely used for creating, composing, and collaborating on complex digital scenes across different tools and pipelines.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc6030b25081909d67488b35a72e05 |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf6fd3b3348190a63bfd29860cc95f |
completed | April 3, 2026, 7:44 a.m. |
Created at: March 30, 2026, 6:46 p.m.