Triple
T28627133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phabricator |
E724553
|
entity |
| Predicate | inspiredFork |
P77442
|
FINISHED |
| Object | Phorge |
—
|
NE NERFINISHED |
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: Phorge | Statement: [Phabricator, inspiredFork, Phorge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredFork Context triple: [Phabricator, inspiredFork, Phorge]
-
A.
inspiredWorks
Indicates that one work served as a source of inspiration or creative influence for the creation or development of another work.
-
B.
inspiredField
Indicates that one entity served as a source of inspiration or influence for the development, direction, or characteristics of a particular field or domain.
-
C.
inspiredSpinOff
chosen
Indicates that one entity served as the creative or conceptual inspiration for another entity that was developed as a spin-off.
-
D.
menuInspiredBy
Indicates that the design, content, or style of one menu is influenced or derived from another source, such as a cuisine, chef, restaurant, or cultural tradition.
-
E.
partlyInspiredBy
Indicates that one entity has been influenced to some extent, but not wholly, by another entity in its creation, development, or form.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 4:36 a.m.