Triple
T15989801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Figma |
E387792
|
entity |
| Predicate | supportsDeveloperHandoffFeature |
P64037
|
FINISHED |
| Object | code inspection |
—
|
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: code inspection | Statement: [Figma, supportsDeveloperHandoffFeature, code inspection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeveloperHandoffFeature Context triple: [Figma, supportsDeveloperHandoffFeature, code inspection]
-
A.
supportsDeveloper
Indicates that one entity provides assistance, resources, or advocacy to help a developer perform their work or achieve their goals.
-
B.
supportsHandoverWith
chosen
Indicates that one entity is capable of transferring control, responsibility, or an ongoing process to another entity in a coordinated handover.
-
C.
supportsDebuggingTools
Indicates that an entity provides or is compatible with tools used for debugging or diagnosing issues.
-
D.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
supportsImageBasedDevelopment
Indicates that one entity enables or facilitates development activities that are driven or guided primarily by images or visual representations.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4e871c819082d7b1c1eaf5b4fe |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.