Triple
T35916607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jira Align |
E1038762
|
entity |
| Predicate | supportsScaleLevel |
P206106
|
FINISHED |
| Object | team level |
—
|
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: team level | Statement: [Jira Align, supportsScaleLevel, team level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsScaleLevel Context triple: [Jira Align, supportsScaleLevel, team level]
-
A.
supportScale
Indicates that one entity enables or accommodates the other’s ability to grow or operate effectively at larger size, capacity, or load.
-
B.
supportsScalingDirection
Indicates that one entity enables or is compatible with a particular direction or mode of scaling (such as scaling up, scaling down, or scaling out) of another entity.
-
C.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
D.
hasPowerScale
Indicates that one entity is associated with a particular scale or measure of power relative to others.
-
E.
coversScale
Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
- F. None of above. chosen
Provenance (4 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:07 p.m.