Triple
T29409059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SyncManager |
E745844
|
entity |
| Predicate | getTagsResolvesTo |
P66401
|
FINISHED |
| Object | sequence of strings |
—
|
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: sequence of strings | Statement: [SyncManager, getTagsResolvesTo, sequence of strings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: getTagsResolvesTo Context triple: [SyncManager, getTagsResolvesTo, sequence of strings]
-
A.
resolvesTo
chosen
Indicates that one entity is mapped, translated, or evaluated into another specific entity as its target or result.
-
B.
hasPhabricatorTag
Indicates that an item (such as a task, revision, or project) is associated with a specific tag within the Phabricator system.
-
C.
hasTaxonomyTag
Indicates that an entity is associated with a specific taxonomy tag used for classification or categorization.
-
D.
hasTagLength
Indicates that an entity is associated with a tag whose length (typically in characters) has a specified value or satisfies a given constraint.
-
E.
supportsTag
Indicates that one entity is capable of recognizing, handling, or being associated with a specified tag.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a36aaec8190b5914c698ba12ee1 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:56 p.m.